On 161230-11:59+0200, Alan McKinnon wrote: > On 30/12/2016 11:44, Nikos Chantziaras wrote: > > A world update emerged gcc-5.4.0-r2 (update from 5.4.0). At the end of > > the build, I got this: > > > > * Python seems to be broken, attempting to locate CHOST ourselves ... > > * Switching native-compiler to x86_64-pc-linux-gnu-5.4.0 > > ...PORTAGE_BZIP2_COMMAND setting is invalid: 'bzip2' > > PORTAGE_BZIP2_COMMAND setting from make.globals is invalid: 'bzip2' > > > > I'm not seeing how python is broken here (works fine), and why > > PORTAGE_BZIP2_COMMAND is invalid. Can someone explain what's going on here? > > > > > > > I get the same odd message for all of the 5.x series for which I have > build logs: > > $ grep -r "Python seems to be broken" /var/log/portage/ > to be broken, attempting to locate CHOST ourselves ... > /var/log/portage/sys-devel:gcc-5.4.0-r2:20161229-080856.log: * Python > seems to be broken, attempting to locate CHOST ourselves ... > to be broken, attempting to locate CHOST ourselves ...
^^^^^^^^^^^^^^^^^^^^ Looking it up, I get this exact same message, plus another for gnueabi: ./cross-arm-unknown-linux-gnueabi:gcc-5.4.0-r2:20161229-131203.log: * Python seems to be broken, attempting to locate CHOST ourselves ... ./sys-devel:gcc-5.4.0-r2:20161229-121300.log: * Python seems to be broken, attempting to locate CHOST ourselves ... > > I suggest file a bug > Yes! Looking it up at: https://bugs.gentoo.org/buglist.cgi?chfield=[Bug%20creation]&chfieldfrom=24h&ctype=atom&title=Bugs%20reported%20in%20the%20last%2024%20hours only this one entry is (currently) about 5.4.0: sys-devel/gcc-5.4.0-r2 has deceitful ${PV} https://bugs.gentoo.org/show_bug.cgi?id=604084 If it is indeed a case for reporting, whoever does it, pls. inform this mailing list, please! -- Miroslav Rovis Zagreb, Croatia http://www.CroatiaFidelis.hr
signature.asc
Description: Digital signature