On Thu, Nov 16, 2023 at 7:42 AM Florian Weimer <fweimer@xxxxxxxxxx> wrote: > > A while back, we made /lib64 a symbolic link to /usr/lib64: > > <https://fedoraproject.org/wiki/Features/UsrMove> > > Is it safe to assume that this symbolic link exists in all chroots? > This includes the initial ramdisk, recovery environments, and chroots > for confining services. > > If we can assume that, we can tell glibc to stop searching for shared > objects in /lib64 in addition to /usr/lib64. It will avoid an > additional failing openat system call if the application calls dlopen > with a shared object name that the system cannot find. > In all practical cases we have, you can make that assumption. -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
