This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: The Linux binutils 2.13.90.0.18 is rleased
- From: Olaf Hering <olh at suse dot de>
- To: Andreas Jaeger <aj at suse dot de>
- Cc: "H. J. Lu" <hjl at lucon dot org>, binutils at sources dot redhat dot com
- Date: Sat, 1 Feb 2003 11:31:11 +0100
- Subject: Re: The Linux binutils 2.13.90.0.18 is rleased
- References: <20030124104903.A26314@lucon.org> <u8fzrgi50p.fsf@gromit.moeb> <20030126103424.GA24408@suse.de>
On Sun, Jan 26, Olaf Hering wrote:
> On Sun, Jan 26, Andreas Jaeger wrote:
>
> >
> > HJ,
> >
> > make check fails on powerpc-linux with:
> > Running /usr/src/packages/BUILD/binutils-2.13.90.0.18/ld/testsuite/ld-elfweak/elfweak.exp ...
> > FAIL: ELF DSO weak data first
> > FAIL: ELF DSO weak data last
> >
> > Any ideas?
>
> Update glibc or try 8.1 based tree?
I tried it again with glibc 2.3 CVS from yesterday:
+ /home/olaf/binutils-2.13.90.0.18/configure --enable-shared --with-gnu-ld --with-gnu-as --host=powerpc-suse-linux --enable-targets=powerpc64-suse-linux
mandarine:~# gcc32/bin/gcc -v
Reading specs from gcc32/bin/../lib/gcc-lib/powerpc-suse-linux/3.2.2/specs
Configured with: /tmp/gcc-3_2-branch/configure --enable-threads=posix --prefix=/home/olaf/gcc32 --enable-languages=c --disable-checking --enable-libgcj --with-system-zlib --enable-shared --enable-__cxa_atexit powerpc-suse-linux
Thread model: posix
gcc version 3.2.2 20030201 (prerelease)
Only these errors:
ERROR: /home/olaf/binutils-2.13.90.0.18/ld/testsuite/ld-selective/3.cc: compilation failed
ERROR: /home/olaf/binutils-2.13.90.0.18/ld/testsuite/ld-selective/4.cc: compilation failed
ERROR: /home/olaf/binutils-2.13.90.0.18/ld/testsuite/ld-selective/5.cc: compilation failed
Hmm, ok, we can ignore that one.
gcc: /home/olaf/binutils-2.13.90.0.18/ld/testsuite/ld-selective/3.cc: C++ compiler not installed on this system
ERROR: /home/olaf/binutils-2.13.90.0.18/ld/testsuite/ld-selective/3.cc: compilation failed
mandarine:~# gcc33/bin/gcc -v
Reading specs from gcc33/bin/../lib/gcc-lib/powerpc-suse-linux/3.3/specs
Configured with: /tmp/gcc-3_3-branch/configure --enable-threads=posix --prefix=/home/olaf/gcc33 --enable-languages=c --disable-checking --enable-libgcj --with-system-zlib --enable-shared --enable-__cxa_atexit powerpc-suse-linux
Thread model: posix
gcc version 3.3 20030201 (prerelease)
/home/olaf/build-binutils33/ld/ld-new -m elf32ppclinux -o tmpdir/libfoo.so -dynamic-linker /lib/ld.so.1 /usr/lib/crt1.o /usr/lib/crti.o /home/olaf/gcc33/li
b/gcc-lib/powerpc-suse-linux/3.3/crtbegin.o --shared tmpdir/bar1a.o tmpdir/foo1a.o -ldl -L/usr/lib /home/olaf/gcc33/lib/gcc-lib/powerpc-suse-linux/3.3/lib
gcc.a /home/olaf/gcc33/lib/gcc-lib/powerpc-suse-linux/3.3/libgcc_eh.a -lc /home/olaf/gcc33/lib/gcc-lib/powerpc-suse-linux/3.3/libgcc.a /home/olaf/gcc33/lib/
gcc-lib/powerpc-suse-linux/3.3/libgcc_eh.a /home/olaf/gcc33/lib/gcc-lib/powerpc-suse-linux/3.3/crtend.o /usr/lib/crtn.o
/home/olaf/build-binutils33/ld/../binutils/objdump --dynamic-syms tmpdir/libfoo.so | grep foo$ > tmpdir/objdump.out
tmpdir/objdump.out: 0: 00010f1c g D .sbss 00000004 Base deallocate_foo
FAIL: ELF DSO weak data first
/home/olaf/build-binutils33/ld/ld-new -m elf32ppclinux -o tmpdir/libfoo.so -dynamic-linker /lib/ld.so.1 /usr/lib/crt1.o /usr/lib/crti.o /home/olaf/gcc33/li
b/gcc-lib/powerpc-suse-linux/3.3/crtbegin.o --shared tmpdir/foo1a.o tmpdir/bar1a.o -ldl -L/usr/lib /home/olaf/gcc33/lib/gcc-lib/powerpc-suse-linux/3.3/lib
gcc.a /home/olaf/gcc33/lib/gcc-lib/powerpc-suse-linux/3.3/libgcc_eh.a -lc /home/olaf/gcc33/lib/gcc-lib/powerpc-suse-linux/3.3/libgcc.a /home/olaf/gcc33/lib/
gcc-lib/powerpc-suse-linux/3.3/libgcc_eh.a /home/olaf/gcc33/lib/gcc-lib/powerpc-suse-linux/3.3/crtend.o /usr/lib/crtn.o
/home/olaf/build-binutils33/ld/../binutils/objdump --dynamic-syms tmpdir/libfoo.so | grep foo$ > tmpdir/objdump.out
tmpdir/objdump.out: 0: 00010f1c g D .sbss 00000004 Base deallocate_foo
FAIL: ELF DSO weak data last
So the bug seems to be real and not related to the gcc3.3-hammer branch.
Anyone else seeing this?
Gruss Olaf
--
A: No.
Q: Should I include quotations after my reply?