| Summary: | sys-devel/gcc with rlibtool: missing linker plugin | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Alex Xu (Hello71) <alex_y_xu> |
| Component: | Current packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | perfect007gentleman |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=924150 https://bugs.gentoo.org/show_bug.cgi?id=931268 https://bugs.gentoo.org/show_bug.cgi?id=931279 https://bugs.gentoo.org/show_bug.cgi?id=922494 |
||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 765709 | ||
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=58128e2701881192e5d551d6b1d27bac3f6cde58 commit 58128e2701881192e5d551d6b1d27bac3f6cde58 Author: Eli Schwartz <eschwartz@gentoo.org> AuthorDate: 2024-09-25 17:51:52 +0000 Commit: Eli Schwartz <eschwartz@gentoo.org> CommitDate: 2024-09-25 18:22:23 +0000 toolchain.eclass: ban the use of rlibtool dev-build/slibtool provides an alternative implementation of libtool which is intended to hook itself into and replace the ltmain.sh-based ./libtool shell scripts installed into an autotools build system. It has some interesting quirks. In particular, it takes the idea of "packagers don't want to install libtool archives for random libraries because nobody uses them and pkg-config is better" and runs with it. It runs quite far with it, as it doesn't install them at all without a new flag passed to slibtool. This is redundant with our existing approach of deleting them in src_install when we know they are useless, and is downright broken in cases such as GCC, where the libtool archives are load-bearing and the resultant compiler is, in their absence, nonfunctional. slibtool supports a variety of wrappers to enable reasonable functionality which it by default disabled. The official recommendation is you are supposed to use "rlibtool" to replace ./libtool as it performs heuristics based on the generated config. But we actually need "rclibtool", which both respects the generated config and also generates the *.la archives and leaves it up to ebuilds to decide whether they should be removed. Raise a fatal error if the user has misconfigured slibtool. This prevents the user from building a broken and malformed GCC. Closes: https://bugs.gentoo.org/932245 Closes: https://bugs.gentoo.org/924150 Closes: https://bugs.gentoo.org/931268 Closes: https://bugs.gentoo.org/931279 Signed-off-by: Eli Schwartz <eschwartz@gentoo.org> Reviewed-by: Sam James <sam@gentoo.org> eclass/toolchain.eclass | 3 +++ 1 file changed, 3 insertions(+) |
when gcc is built with LIBTOOL=rlibtool, linker plugin is disabled ("checking linker plugin support... 0"), because gcc/configure.ac checks test -f liblto_plugin.la. LIBTOOL=rclibtool resolves the issue.