Bug#334673: libc6-dev-amd64: Cannot link 64-bit programs
On Wed, Oct 19, 2005 at 09:48:46AM +0200, Daniel Schepler wrote: > Package: libc6-dev-amd64 > Severity: important > Version: 2.3.5-7 > > When I try linking a simple test program in 64-bit mode, I get: > > frobnitz:/tmp/buildd# gcc -m64 -o test test.c > /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 > > If I create a symlink /lib/ld-linux-x86-64.so.2 -> > /lib64/ld-linux-x86-64.so.2, the link stage succeeds -- but that might > not be a proper solution in general. (Especially if it also happens > with other binary dependencies between 64-bit libraries, which I > haven't been able to test.) > > I don't know whether this is actually a problem in the glibc, gcc, or > binutils packages -- feel free to reassign, or clone/block, as > appropriate. Binutils, temporary. As a workaround, you can either add the lib64 directories to ld.so.conf, or install amd64-libs (which will do that for you, until binutils is fixed, and have a dependency on the fixed binutils after). -- Daniel Jacobowitz CodeSourcery, LLC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#334673: libc6-dev-amd64: Cannot link 64-bit programs
Package: libc6-dev-amd64 Severity: important Version: 2.3.5-7 When I try linking a simple test program in 64-bit mode, I get: frobnitz:/tmp/buildd# gcc -m64 -o test test.c /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 If I create a symlink /lib/ld-linux-x86-64.so.2 -> /lib64/ld-linux-x86-64.so.2, the link stage succeeds -- but that might not be a proper solution in general. (Especially if it also happens with other binary dependencies between 64-bit libraries, which I haven't been able to test.) I don't know whether this is actually a problem in the glibc, gcc, or binutils packages -- feel free to reassign, or clone/block, as appropriate. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-686 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
