Nikos Chantziaras <rea...@gmail.com> writes: > 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?
Since there is such a command, is it possible (and worthwhile) to use lbzip2 instead of bzip2 with portage? (lbzip2 is ridiculously fast when you have the cores and the RAM ...)
