The new 1.89 revision of /usr/portage/eclass/toolchain-funcs.eclass causes numerous ebuild failures throughout portage. These failures appear to manifest as the following error(s): making executable: [insert random library here].so.* making executable: [insert random library here].so.* * QA Notice: Missing gen_usr_ldscript for [insert random library here].so * QA Notice: Missing gen_usr_ldscript for [insert random library here].so * * ERROR: sys-apps/openrc-0.4.3-r1 failed. * Call stack: * misc-functions.sh, line 717: Called install_qa_check * misc-functions.sh, line 329: Called die * The specific snippet of code: * [[ ${abort} == "yes" ]] && die "add those ldscripts" * The die message: * add those ldscripts * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/sys-apps/openrc-0.4.3-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-apps/openrc-0.4.3-r1/temp/environment'. This is explicitly caused by changes to toolchain-funcs.eclass. Revision 1.88 of toolchain-funcs.eclass works correctly, and this error does /not/ present itself (thus allowing the ebuild to install). Downloading and installing Rev 1.88 and copying it to /usr/portage/eclass by hand solves the above issue introduced by any recent sync that happened to carry 1.89 of toolchain-funcs.eclass with it. Reproducible: Always Steps to Reproduce: 1. emerge --sync 2. emerge openrc || device-mapper || others?? 3. QA Notice will appear during install and bomb out on gen_usr_ldscript Actual Results: See above. Expected Results: Emerge should complete successfully.
Confirming, happens here during minimal 2008.0 x86 install
confirmed, Revision 1.88 of toolchain-funcs.eclass works correctly
I reverted the last commit entirely. I'm very sorry for the caused problems.
thank you very much
*** Bug 264979 has been marked as a duplicate of this bug. ***
*** Bug 265003 has been marked as a duplicate of this bug. ***
*** Bug 265004 has been marked as a duplicate of this bug. ***
*** Bug 265015 has been marked as a duplicate of this bug. ***
*** Bug 264977 has been marked as a duplicate of this bug. ***
*** Bug 260131 has been marked as a duplicate of this bug. ***
