Summary: | app-arch/tar: USE=static breaks every time glibc upgrades (was: glibc causes tar to Segmentation fault in NSS) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Nuno <can.ecodo.nu.n.o+bugs.gentoo> |
Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | toolchain |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=741116 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Nuno
2021-01-04 21:29:39 UTC
Yes, USE=static requires that programs not to use NSS facility (that requires dynamic library loading and has to match glibc versions at runtime and static link time). In bug #741116 rsync lost USE=static precisely due to this problem. If `tar` has no special provision to work in USE=static it should also not provide known-broken option. At a glance on the ebuild it does only `use static && append-ldflags -static` which is not enough. Reassigning to base-system@ to remove USE=static. To restore a system to working state I suggest you to pick working tar and rsync from a recent gentoo stage3 build. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1766e2a34d57bf77074164320d0d417d3162f6ee commit 1766e2a34d57bf77074164320d0d417d3162f6ee Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2021-01-04 22:37:26 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2021-01-04 22:37:26 +0000 app-arch/tar: drop 'static' USE flag Closes: https://bugs.gentoo.org/763585 Signed-off-by: Mike Gilbert <floppym@gentoo.org> app-arch/tar/{tar-1.32.ebuild => tar-1.32-r1.ebuild} | 15 +++++++-------- .../tar/{tar-1.32.90.ebuild => tar-1.32.90-r1.ebuild} | 19 ++++++++++--------- 2 files changed, 17 insertions(+), 17 deletions(-) |