xxx failed on amd64
Jean-Baptiste Quenot
jbq at caraldi.com
Fri Nov 17 03:30:45 PST 2006
* Kris Kennaway:
> FYI; can you please investigate and/or report to the developers?
> ...
> ===> Building for resin-2.1.17_1
> ...
> cc -shared -o common.o stream.o registry.o config.o memory.o
> /usr/bin/ld: stream.o: relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC
> stream.o: could not read symbols: Bad value
* Kris Kennaway:
> FYI; can you please investigate and/or report to the developers?
> ...
> ===> Building for resin-3.0.21
> ...
> cc -shared -L/usr/lib -o libresin_os.so jni_os.o jni_jvmti.o jni_jvmdi.o -pthread
> /usr/bin/ld: jni_os.o: relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC
> jni_os.o: could not read symbols: Bad value
I don't see the point of adding special treatment of amd64 in all
my ports that use gcc. Why this is not handled by the ports
infrastructure? Is it satisfactory to copy/paste the three needed
lines in all ports?
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
More information about the freebsd-ports
mailing list