On Sat, Apr 08, 2006 at 01:21:00PM +0200, Martin Michlmayr wrote: > 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.
I think this is a bug in gcc-4.1. is_safe() is static, so it shouldn't show up for the linker in the first place. caudium.o build with gcc-4.0 gives: $ objdump -t caudium.o |grep is_safe 000000000000497e l F .text 0000000000000041 is_safe $ objdump -r caudium.o |grep is_safe With gcc-4.1: $ objdump -t caudium.o |grep is_safe 0000000000000000 *UND* 0000000000000000 is_safe $ objdump -r caudium.o |grep is_safe 0000000000004677 R_X86_64_PC32 is_safe+0xfffffffffffffffc What gcc-4.1 generated doesn't look right to me. Note that this was all without any -O. If I compile it with gcc-4.1 with -O instead, I get: $ objdump -t caudium.o |grep is_safe 0000000000000053 l F .text 0000000000000029 is_safe $ objdump -r caudium.o |grep is_safe (One has to wonder why they make use of inline if they don't even use -O.) Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
