Manoj Dayaram

Actually, that would depend on whether the linkers used can link a library that was not compiled for this system, and I doubt the linker in a linux computer knows...

Sorry for the delay on feedback for this, slipped through the cracks. Anyways, I'm having a hard time wrapping my head around it all. Can you provide an example program...

Hmmmm, I wonder, @hcatlin, do you remember why the choice was made to make the encoding inputs byte arrays instead of strings?

I'm fine with updating the API, specially since all errors would be flagged at compile time and are easily fixed by typecasting to string anyways. As long as we're sure...

Hmm, interesting. We currently don't have any plans to support SAX style parsing. If you're feeling ambitious, I'd say go for it! I believe libxml has some support for it.

Commenting the call to `exec_xpath_function` on this line seems to make the compiler happy: https://github.com/moovweb/gokogiri/blob/master/xpath/xpath.go#L20

I should say, tried compiling with `go1.2rc2` and the error still exists.

Made internal branch `mw_master` with the above line commented out so that we can continue building for the time being. I'll keep the bug in master for reference until it...

Some more debug info, running `go test -x gokogiri/xpath` ``` $ go test -x -ldflags -extldflags=-L/Users/Shared/JenkinsNet/Home/workspace/manhattan-4.8-build/label/darwin_amd64/.build-sandbox/clibs/lib . WORK=/tmp/go-build533157375 mkdir -p $WORK/gokogiri/xpath/_test/gokogiri/ mkdir -p $WORK/gokogiri/util/_obj/ mkdir -p $WORK/gokogiri/ cd /Users/Shared/JenkinsNet/Home/workspace/manhattan-4.8-build/label/darwin_amd64/.build-sandbox/src/gokogiri/util /Users/jenkins/.gvm/gos/go1.2rc2/pkg/tool/darwin_amd64/6g...

Hmmm, unfortunately, that did not help. I filed a new issue in code.google.com: https://code.google.com/p/go/issues/detail?id=6661&thanks=6661&ts=1382660533