Bug#334673: libc6-dev-amd64: Cannot link 64-bit programs

[Daniel Jacobowitz <drow@false.org>]

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 `_rtld_global@GLIBC_PRIVATE'
> /lib64/libc.so.6: undefined reference to `__libc_enable_secure@GLIBC_PRIVATE'
> /lib64/libc.so.6: undefined reference to `_rtld_global_ro@GLIBC_PRIVATE'
> /lib64/libc.so.6: undefined reference to `_dl_out_of_memory@GLIBC_PRIVATE'
> /lib64/libc.so.6: undefined reference to `_r_debug@GLIBC_2.2.5'
> /lib64/libc.so.6: undefined reference to `__tls_get_addr@GLIBC_2.3'
> /lib64/libc.so.6: undefined reference to `_dl_argv@GLIBC_PRIVATE'
> 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