Bug#1120508: Inconsistency between linker script and package content

Package: libc6-dev

Version: 2.42-2

Severity:minor

The development package of libc6 provides a linker script `/usr/lib/x86_64-linux-gnu/libc.so` where the content is the following on a x86-64 platform:

````
/* GNU ld script

Use the shared library, but some functions are only in

the static library, so try that secondarily. */

OUTPUT_FORMAT(elf64-x86-64)

GROUP ( /lib/x86_64-linux-gnu/libc.so.6 /usr/lib/x86_64-linux-gnu/libc_nonshared.a AS_NEEDED ( /lib64/ld-linux-x86-64.so.2 ) )
````

The package depends from libc6 which provides the shared library file `/usr/lib/x86_64-linux-gnu/libc.so.6`.
As far as I can tell, there is no reason why the linker script should reference to /lib instead of /usr/lib. Same applies for `/lib64/ld-linux-x86-64.so.2`referenced in the linker script.
In addition to the libc.so file, libm.so linker script is also affected.

In my case, the current situation is somewhat inconvenient because I want to use it to create a sysroot for a cross-build environment in Windows, and symbolic links are somewhat problematic there.

Reply to: