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/ /var/log/portage/sys-devel:gcc-5.3.0:20161009-190108.log: * Python seems 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 ... /var/log/portage/sys-devel:gcc-5.4.0:20161009-182055.log: * Python seems to be broken, attempting to locate CHOST ourselves ... The 4.x series is fine. I suggest file a bug -- Alan McKinnon alan.mckin...@gmail.com
