Hi, I noticed a /usr/include/crypt.h file conflict when installing glibc headers-only on a rootfs which is using sys-libs/libxcrypt installed as a system library. This is due to glibc not respecting the crypt use flag, which if disabled should not install either crypt.h or the glibc libcrypt. I have created a pull request to fix the issue: https://github.com/gentoo/gentoo/pull/26747 Reproducible: Always Steps to Reproduce: 1. Build glibc with headers-only enabled and see crypt.h is installed regardless of the crypt use flag value. Actual Results: crypt.h is always installed by glibc Expected Results: crypt.h should not be installed when the crypt use flag is disabled
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=77cec48da70c6d6424ed6dba4357dd8eacd262c2 commit 77cec48da70c6d6424ed6dba4357dd8eacd262c2 Author: Adrian Ratiu <adrian.ratiu@collabora.com> AuthorDate: 2022-08-05 12:41:45 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-08-20 00:58:58 +0000 sys-libs/glibc: make crypt.h install depend on crypt use flag The crypt use flag is supposed to control whether libcrypt and its associated crypt.h are installed, but it's ignored in header-only builds and crypt.h is always installed. This generates a conflict for eg with sys-libs/libcxrypt installed as a system lib which provides /usr/include/crypt.h even if glibc is built with -crypt. The solution is for glibc to properly respect the crypt use flag when installing the headers. Fixes: https://bugs.gentoo.org/863812 Signed-off-by: Adrian Ratiu <adrian.ratiu@collabora.com> Closes: https://github.com/gentoo/gentoo/pull/26747 Signed-off-by: Sam James <sam@gentoo.org> sys-libs/glibc/{glibc-2.33-r13.ebuild => glibc-2.33-r14.ebuild} | 1 + sys-libs/glibc/{glibc-2.34-r13.ebuild => glibc-2.34-r14.ebuild} | 1 + sys-libs/glibc/glibc-2.35-r8.ebuild | 1 + sys-libs/glibc/glibc-2.36.ebuild | 1 + sys-libs/glibc/glibc-9999.ebuild | 1 + 5 files changed, 5 insertions(+)
