On 2018-01-24 17:08, Javier Serrano Polo wrote: > Source: glibc > Version: 2.26-4 > Severity: wishlist > > amd64 systems can work perfectly without a /lib64 directory. Since I am > unlikely to convince you to ship ld-linux-x86-64.so.2 under /lib instead I am not convinced about that. The dynamic linker path is part of the x86-64 ABI and is present in all ELF executables. Moving it means rebuilding all the packages. It should probably be done using a different architecture than "amd64". Could you please explain it how it works and what would be the use case? > of /lib64 by default, could you allow this option with a build profile, > e.g. nolib64? I am not convinced we want to add extra complexity in our already complex makefiles and maintainer scripts unless there is a real use case. This tend to bitrot and break other parts of the code. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien@aurel32.net http://www.aurel32.net
Attachment:
signature.asc
Description: PGP signature