Bug#1120508: Inconsistency between linker script and package content

[Aurelien Jarno <aurel32@debian.org>]

Hi,

On 2025-11-11 12:12, KOCH.Martin wrote:
> 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.

Indeed, this is a leftover from the badly handled usr-merge transition, 
the file used to be in /lib before. I'll see what can be done.

> Same applies for `/lib64/ld-linux-x86-64.so.2`referenced in the linker script.

No, the linker script is part of the ELF ABI, so this must not be changed.

> In addition to the libc.so file, libm.so linker script is also affected.

Indeed.

Regards
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                     http://aurel32.net