View previous topic :: View next topic |
Author |
Message |
CaptainBlood Advocate
Joined: 24 Jan 2010 Posts: 3661
|
Posted: Wed Apr 10, 2024 6:18 pm Post subject: Easy filter-lto per package cancellation? |
|
|
Looking for a easy way to workaround filter-lto.
The weakest way I see it is to:
Duplicate original ebuild in local repository.
Optionally revbump final build.
Optionally unkeyword revbumped ebuild.
Edit filter-lto directive.
Emerge new ebuild.
If possible if would be easier to only:
Duplicate original ebuild in [a dedicated] local repository.
Emerge new ebuild.
IIUC, that would require the containing local to be set in a way that would keep all the selected profile mechanisms but filter-lto one,
I went through the gentoo profile support, without working it out.
Any practical [generic] example for such a portage [alike] feature overload?
Thks 4 ur attention, interest & support. _________________ USE="-* ..." in /etc/portage/make.conf here, i.e. a countermeasure to portage implicit braces, belt & diaper paradigm
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. " |
|
Back to top |
|
|
Hu Administrator
Joined: 06 Mar 2007 Posts: 21867
|
Posted: Wed Apr 10, 2024 7:08 pm Post subject: |
|
|
Add an on-sync hook to patch flag-o-matic.eclass with the following: Code: | --- a/eclass/flag-o-matic.eclass
+++ b/eclass/flag-o-matic.eclass
@@ -273,6 +273,10 @@
# Remove flags that enable LTO and those that depend on it
filter-lto() {
[[ $# -ne 0 ]] && die "filter-lto takes no arguments"
+ if [[ -n "${I_KNOW_I_WANT_TO_USE_LTO}" ]]; then
+ ewarn "$P called filter-lto; ignoring. DO NOT FILE BUGS ABOUT THIS PACKAGE."
+ return
+ fi
filter-flags '-flto*' -fwhole-program-vtables '-fsanitize=cfi*'
}
| Then set the corresponding environment variable using package.env. |
|
Back to top |
|
|
CaptainBlood Advocate
Joined: 24 Jan 2010 Posts: 3661
|
Posted: Wed Apr 10, 2024 7:19 pm Post subject: |
|
|
Wow, impressively quick response.
Currently stuck with a heavily swapping emerge...
Can't wait to test this
Thks 4 ur attention, interest & support. _________________ USE="-* ..." in /etc/portage/make.conf here, i.e. a countermeasure to portage implicit braces, belt & diaper paradigm
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. " |
|
Back to top |
|
|
CaptainBlood Advocate
Joined: 24 Jan 2010 Posts: 3661
|
Posted: Wed Apr 10, 2024 10:19 pm Post subject: |
|
|
Hu wrote: | Add an on-sync hook to patch... |
Isn't postsync hook' (Wiki) more accurate, or is it?
Thks 4 ur attention, interest & support. _________________ USE="-* ..." in /etc/portage/make.conf here, i.e. a countermeasure to portage implicit braces, belt & diaper paradigm
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. " |
|
Back to top |
|
|
Hu Administrator
Joined: 06 Mar 2007 Posts: 21867
|
Posted: Thu Apr 11, 2024 12:24 am Post subject: |
|
|
Yes, that is a way you could arrange for the patch to be applied at the proper time. |
|
Back to top |
|
|
CaptainBlood Advocate
Joined: 24 Jan 2010 Posts: 3661
|
Posted: Sat May 04, 2024 7:16 pm Post subject: |
|
|
Using patched portage tree via rsync on local net fails on verification.
Needs to be fixed...
Working on it...
Thks 4 ur attention, interest & support. _________________ USE="-* ..." in /etc/portage/make.conf here, i.e. a countermeasure to portage implicit braces, belt & diaper paradigm
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. " |
|
Back to top |
|
|
|