On Sat, Apr 08, 2006 at 01:21:00PM +0200, Martin Michlmayr scribbled: > reopen 358261 > retitle 358261 FTBFS with GCC 4.1: Not using -fPIC to make shared lib. > thanks > > It seems this is still there, but it worked on the official auto > builder so I wonder if this is due to a) using GCC 4.1 (instead of > 4.0) or b) using the unofficial archive. > > [checks...] > > Okay, I only see this error with GCC 4.1, not with 4.0. Note however that the command line below does have -fPIC - smartlink merely strips the -R parameters and passes the rest to gcc as they are. Perhaps gcc 4.1 requires the use of -fpic instead (although -fPIC should work then too...)? > > > Automatic build of caudium_2:1.4.7-14 on em64t by sbuild/amd64 1.112 > ... > > /build/tbm/caudium-1.4.7/smartlink gcc -shared -fPIC -R/usr/lib -L/usr/lib -R/usr/local/lib -L/usr/local/lib -R/usr/X11R6/lib -L/usr/X11R6/lib -o _Caudium.so caudium.o nb_send.o getdate.o datetime.o entparse.o scratchpad.o /usr/lib/gcc/x86_64-linux-gnu/4.1.0/libgcc.a -lc /usr/lib/gcc/x86_64-linux-gnu/4.1.0/libgcc.a > > /usr/bin/ld: caudium.o: relocation R_X86_64_PC32 against `is_safe' can not be used when making a shared object; recompile with -fPIC > > /usr/bin/ld: final link failed: Bad value > > collect2: ld returned 1 exit status best regards, marek
Attachment:
signature.asc
Description: Digital signature