|
Description
Sergei Trofimovich
2020-01-18 22:40:36 UTC
A rather exhaustive list of failing packages is here: https://github.com/vaeth/portage-env-mv/blob/master/package.cflags/checks (In reply to Martin Väth from comment #1) > A rather exhaustive list of failing packages is here: > https://github.com/vaeth/portage-env-mv/blob/master/package.cflags/checks To ease fixing them I suggest filing upstream bugs (and/or gentoo downstream bugs) for packages instead of just linking them here. SUSE also found a bunch of failures: https://bugzilla.suse.com/show_bug.cgi?id=1160244 FYI: GentooLTO also has a list of `-fno-common` workarounds too: https://github.com/InBetweenNames/gentooLTO/blob/05965d113f5da37fc5428de658fb3c25016bf3c9/sys-config/ltoize/files/package.cflags/ltoworkarounds.conf#L272 A few users in the overlay have been running `-fno-common` for quite some time now. (In reply to Shane Peelar from comment #5) > FYI: GentooLTO also has a list of `-fno-common` workarounds too: > > https://github.com/InBetweenNames/gentooLTO/blob/ > 05965d113f5da37fc5428de658fb3c25016bf3c9/sys-config/ltoize/files/package. > cflags/ltoworkarounds.conf#L272 > > A few users in the overlay have been running `-fno-common` for quite some > time now. Please report new individual package failures as blockers to this bug. (In reply to Sergei Trofimovich from comment #6) > Please report new individual package failures as blockers to this bug. Will do. It looks like I have about 41 packages to report with `-fcommon` related issues -- is there a convenient way to create bugs for these or will I have to manually enter each individual one? They're straight from GentooLTO, and they have not been reported here yet. (In reply to Shane Peelar from comment #8) > It looks like I have about 41 packages to report with `-fcommon` related > issues -- is there a convenient way to create bugs for these or will I have > to manually enter each individual one? They're straight from GentooLTO, and > they have not been reported here yet. Bugs like bug #722286 are not very useful without 'emerge --info' and 'build.log'. New bugs are easy to create programmatically. An example of pre-filled bugs is https://bugs.gentoo.org/708912#c1. But it's a topic outside of this bug. FYI: even more bugs in conjunction with "-flto". It affect conftest in libtool configure (global sys-devel/libtool and packaged separately), so variable global_symbol_pipe (in libtool) will be empty. PS Yes, I know - LTO is not mainstream-supported... PPS To workaround "-fno-common -flto" problem - simple predefine in make.conf: lt_cv_sys_global_symbol_pipe='sed -n -e '\''s/^.*[ ]\([ABCDGIRSTW][ABCDGIRSTW]*\)[ ][ ]*\([_A-Za-z][_A-Za-z0-9]*\)$/\1 \2 \2/p'\'' | sed '\''/ __gnu_lto/d'\''' but better (to avoid copy-paste issues) to take it from here: https://raw.githubusercontent.com/mahatma-kaganovich/raw/master/profiles/common/_lto/make.defaults (In reply to Denis Kaganovich from comment #10) > FYI: even more bugs in conjunction with "-flto". It affect conftest in > libtool configure (global sys-devel/libtool and packaged separately), so > variable global_symbol_pipe (in libtool) will be empty. > > PS Yes, I know - LTO is not mainstream-supported... That is probably a bug #708340. I suggest continuing it there. |