On Sat, Oct 15, 2005 at 01:00:37PM +0200, Matthias Klose wrote: > Mark Brown writes: > > On Sat, Oct 15, 2005 at 11:29:15AM +0200, Matthias Klose wrote: > > > Mark Brown writes: > > > > > > We don't build biarch for PowerPC? > > > > > well, yes, but the patch is in the archive as well. > > > > Hrm... Interesting. > > > > I see that the new glibc is still only in incoming. I've pulled it from > > there but I'm running into trouble getting it to build applications: > > > > | gcc -m64 -c -o hello.o hello.c > > | gcc -m64 -o hello hello.o > > | /usr/bin/ld: warning: ld-linux-x86-64.so.2, needed by /lib64/libc.so.6, > > not found (try using -rpath or -rpath-link) > > | /lib64/libc.so.6: undefined reference to [EMAIL PROTECTED]' > > | /lib64/libc.so.6: undefined reference to [EMAIL PROTECTED]' > > | /lib64/libc.so.6: undefined reference to [EMAIL PROTECTED]' > > | /lib64/libc.so.6: undefined reference to [EMAIL PROTECTED]' > > | /lib64/libc.so.6: undefined reference to [EMAIL PROTECTED]' > > | /lib64/libc.so.6: undefined reference to [EMAIL PROTECTED]' > > | /lib64/libc.so.6: undefined reference to [EMAIL PROTECTED]' > > | collect2: ld returned 1 exit status > > > > Is there something I need beyond libc6-dev-amd64 and the packages it > > depends on (including lib64gcc1)? I have gcc 4.0.2-1 installed. > > it builds on am64 in a i386 chroot, but I see this failure as well, > when building on a i386 host.
This is a binutils bug. I discussed it with James Troup last night, and we'll get a binutils upload to fix it in the near future; in the mean time, just install amd64-libs 1.3, or add /lib64 and /usr/lib64 to /etc/ld.so.conf. The problem is that ld used to find the 64-bit libraries by searching /etc/ld.so.conf; which was fine for amd64-libs which added /lib64 to ld.so.conf so that ldconfig would find them; but now the new ldconfig knows to search there automatically, so the directory is not added to ld.so.conf; but ld's search path does not include /lib64 (yet). Ryan, this doesn't answer why the i386 buildd picked it up, but does answer why it failed. -- Daniel Jacobowitz CodeSourcery, LLC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
