Open GoogleCodeExporter opened 9 years ago
I did the following
mkdir -p $GOROOT/pkg
it created a pkg dir in repo but now it gives the error as below
%%%% making libcgo %%%%
gcc -m32 -O2 -fPIC -o linux_386.o -c linux_386.c
gcc -m32 -O2 -fPIC -o 386.o -c 386.S
gcc -m32 -O2 -fPIC -o util.o -c util.c
linux_386.c:1:0: warning: -fPIC ignored for target (all code is position
independent)
386.S:1:0: warning: -fPIC ignored for target (all code is position independent)
util.c:1:0: warning: -fPIC ignored for target (all code is position independent)
gcc -m32 -shared -lpthread -lm -o libcgo.so linux_386.o 386.o util.o
Cannot export crosscall_386: symbol not defined
linux_386.o:linux_386.c:(.text+0x4c): undefined reference to `_crosscall_386'
collect2: ld returned 1 exit status
Makefile:27: recipe for target `libcgo.so' failed
make: *** [libcgo.so] Error 1
From $GOROOT, "cd src/libcgo"
What is the expected output? What do you see instead?
Should compile, but it gets link error since it cannot find the symbol
"_crosscall_386". The method "crosscall_386" is defined in
"src/libcgo/386.S".
made changes to as below in 386.S
#define EXT(s) s
.globl EXT(_crosscall_386)
EXT(_crosscall_386):
pushl %ebp
movl %esp, %ebp
this come to new error as
cd xml && make install
make[1]: Entering directory
`/cygdrive/f/projects/go/golang-on-cygwin/src/pkg/xml'
cp _obj/xml.a /cygdrive/f/projects/go/golang-on-cygwin/pkg/linux_386/xml.a
make[1]: Leaving directory
`/cygdrive/f/projects/go/golang-on-cygwin/src/pkg/xml'
cd archive/tar && make test
make[1]: Entering directory
`/cygdrive/f/projects/go/golang-on-cygwin/src/pkg/archive/tar'
gotest
make[1]: gotest: Command not found
/cygdrive/f/projects/go/golang-on-cygwin/src/Make.pkg:35: recipe for target
`test' failed
make[1]: *** [test] Error 127
make[1]: Leaving directory
`/cygdrive/f/projects/go/golang-on-cygwin/src/pkg/archive/tar'
Makefile:132: recipe for target `archive/tar.test' failed
make: *** [archive/tar.test] Error 2
Original comment by kanakdee...@gmail.com
on 27 Aug 2012 at 5:28
The _crosscall_386 error looks like issue #3.
Original comment by thuk...@gmail.com
on 17 Dec 2012 at 11:14
Original issue reported on code.google.com by
kanakdee...@gmail.com
on 26 Aug 2012 at 9:54