On Sun, Apr 27, 2008 at 02:41:49PM +0200, Luk Claes wrote: > Jörg Sommer wrote: > > Hallo Kurt, > > > > Kurt Roeckx schrieb am Sun 27. Apr, 13:10 (+0200): > >> On Sun, Apr 27, 2008 at 02:26:27AM +0200, Jörg Sommer wrote: > >>> Kurt Roeckx schrieb am Sat 26. Apr, 22:17 (+0200): > >>>> On Sat, Apr 26, 2008 at 08:38:51PM +0200, Jörg Sommer wrote: > >>>>> Kurt Roeckx schrieb am Sat 26. Apr, 19:33 (+0200): > >>>>>> Package: slrn > >>>>>> Version: 0.9.9~pre102-1 > >>>>>> Severity: serious > >>>>>> > >>>>>> Hi, > >>>>>> > >>>>>> Your package is failing to build with the following error: > >>>>>> checking for gcc... gcc > >>>>>> checking for C compiler default output file name... > >>>>>> configure: error: C compiler cannot create executables > >>>>>> See `config.log' for more details. > >>>>> Can you send me the config.log? > >>>> This should be easy to reproduce in a current unstable environment. > >>> Which compiler version do you use? 4.3? > >> The default on i386 and amd64 still is gcc-4.2. The latest version > >> in unstable is 4.2.3-3. > > > > Err, bad. > > > >>>> Anyway, this is what I get in config.log: > >>>> configure:2586: checking for C compiler default output file name > >>>> configure:2613: gcc -g -O2 -Wall -g -O2 -fPIC -fPIE -fstack-protector > >>>> -Wformat=2 -Wextra -D_FORTIFY_SOURCE=2 -Wl,-zrelro,-pie conftest.c >&5 > >>>> /usr/bin/ld: > >>>> /usr/lib/gcc/x86_64-linux-gnu/4.2.3/../../../../lib64/crt1.o: relocation > >>>> R_X86_64_32S against `__libc_csu_fini' can not be used when making a > >>>> shared object; recompile with -fPIC > >>>> /usr/lib/gcc/x86_64-linux-gnu/4.2.3/../../../../lib64/crt1.o: could not > >>>> read symbols: Bad value > >>> ^^^^^ > >>> Please, update your compiler. There seems to be bug in 4.2. > >> It is the latest compiler. And it's also the default one. > > > > Can you try to build with gcc-4.3? Run "CC=gcc-4.3 dpkg-buildpackage". > > > >> Note that it's complaining about /usr/lib/crt1.o which is part of > >> libc6-dev. So if anything should be upgraded it's that. That's also > >> the latest version: 2.7-10 > > > > I'll ask debian-devel what's broken. > > Did you already try to make sure that when -g -O2 is not used twice as > options it still fails? The -g -O2 is what the new dpkg initiates the > CFLAGS with AFAIK...
It has nothing to do with it. It's the "-Wl,-pie" part that is the problem. Using gcc-4.3 of course has the same problem. As far as I can see this is a problem of the linker. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
