On Wed, Jan 24, 2018 at 10:57:20PM +0100, Javier Serrano Polo wrote:
> El dc 24 de 01 de 2018 a les 22:40 +0100, Sven Joachim va escriure:
> > Well, then you have to live with /lib64.
>
> I do not live with /lib64. You do not have to live with /lib64 unless
> you want to.
That path is baked into
On 2018-01-24 21:05, Javier Serrano Polo wrote:
> X-Debbugs-CC: cl...@debian.org
>
> El dc 24 de 01 de 2018 a les 18:26 +0100, Aurelien Jarno va escriure:
> > The dynamic linker path is part of the
> > x86-64 ABI and is present in all ELF executables.
>
> I am aware that the original
On 2018-01-24 21:05 +0100, Javier Serrano Polo wrote:
> El dc 24 de 01 de 2018 a les 18:26 +0100, Aurelien Jarno va escriure:
>> The dynamic linker path is part of the
>> x86-64 ABI and is present in all ELF executables.
>
> I am aware that the original specification has that quirk, but it was
>
On Wed, Jan 24, 2018 at 9:26 AM, Aurelien Jarno wrote:
> 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
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
> "AJ" == Aurelien Jarno writes:
AJ> No, that simply doesn't scale. Other packages than the one in src:glibc
AJ> depends on libc6 >= 2.26, and more and more are going to pick up this
AJ> dependency in the next months. They might also be unpacked before libc6
AJ> preinst
6 matches
Mail list logo