Summary: | sys-fs/fuse-3.11.0: build fails with -flto=thin: default version symbol fuse_loop_mt@@FUSE_3.2 must be defined | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | nvinson234 |
Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | juippis |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=852929 https://bugs.gentoo.org/show_bug.cgi?id=852917 https://github.com/libfuse/libfuse/issues/198 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 618550 | ||
Attachments: |
build.log
fuse-3.11.0.ebuild synthetic for no-lto vs lto package file size |
Description
nvinson234
2022-06-19 12:31:02 UTC
Created attachment 786161 [details]
build.log
Created attachment 786164 [details]
fuse-3.11.0.ebuild
updated ebuild that replaces -flto=thin with -flto as pciutils builds when -flto is set.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5171d41e43c3f8e7015399e5a8f9158a430596b2 commit 5171d41e43c3f8e7015399e5a8f9158a430596b2 Author: Sam James <sam@gentoo.org> AuthorDate: 2023-01-14 16:17:05 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-01-14 16:17:30 +0000 sys-fs/fuse: filter-lto As usual, needing thin is a sign that something is wrong, and it may be unsafe at runtime if it even builds. Closes: https://bugs.gentoo.org/853058 Signed-off-by: Sam James <sam@gentoo.org> sys-fs/fuse/{fuse-3.13.0.ebuild => fuse-3.13.0-r1.ebuild} | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) Created attachment 848463 [details]
synthetic for no-lto vs lto package file size
gcc lto working fine here;
smaller size as expected here.
(In reply to CaptainBlood from comment #4) > Created attachment 848463 [details] > synthetic for no-lto vs lto package file size > > gcc lto working fine here; > smaller size as expected here. I'm not sure what your point is. They clearly don't do symbol versioning correctly, hence unsafe and can't be relied on. If you want to use it at your own risk, go wild. |