Hi,
Sergey Bugaev skribis:
> On Fri, May 19, 2023 at 2:52 PM Carlos O'Donell wrote:
>> Removing configuration options and making it simple to configure and use
>> glibc is great
>> goal. I think that ldconfig should always be enabled and I don't see a
>> downside to making
>> `use_ldconfig=ye
Hello,
On Fri, May 19, 2023 at 3:30 PM Florian Weimer wrote:
> Debian hasn't upstreamed there multi-arch path layouts. We could
> implement multi-arch ldconfig in /etc/ld.so.cache, but with the paths
> that Debian currently uses, it's not easy because there's no automated
> way ldconfig can reco
* Sergey Bugaev via Libc-alpha:
> Moreover, Debian GNU/Hurd, the primary Hurd-based distribution, has been
> shipping ld.so.cache on Hurd as a downstream patch [1] (note that more
> changes would be required for x86_64-gnu because of FLAG_X8664_LIB64).
> They don't really have a choice, it seems:
On 5/17/23 14:54, Sergey Bugaev via Libc-alpha wrote:
> Hello,
>
> having set up a very basic x86_64-gnu system to debug startup issues, I
> was surprised to discover that my self-built ld.so does not look for the
> shared libraries in /lib/x86_64-gnu/ (which is where Samuel Thibault's deb
> packa
Hello,
having set up a very basic x86_64-gnu system to debug startup issues, I
was surprised to discover that my self-built ld.so does not look for the
shared libraries in /lib/x86_64-gnu/ (which is where Samuel Thibault's deb
packages place them) at all. I then learned that ld.so.cache and ldconf
