| 1 |
Nikos Chantziaras <realnc@×××××.com> writes: |
| 2 |
|
| 3 |
> A world update emerged gcc-5.4.0-r2 (update from 5.4.0). At the end of |
| 4 |
> the build, I got this: |
| 5 |
> |
| 6 |
> * Python seems to be broken, attempting to locate CHOST ourselves ... |
| 7 |
> * Switching native-compiler to x86_64-pc-linux-gnu-5.4.0 |
| 8 |
> ...PORTAGE_BZIP2_COMMAND setting is invalid: 'bzip2' |
| 9 |
> PORTAGE_BZIP2_COMMAND setting from make.globals is invalid: 'bzip2' |
| 10 |
> |
| 11 |
> I'm not seeing how python is broken here (works fine), and why |
| 12 |
> PORTAGE_BZIP2_COMMAND is invalid. Can someone explain what's going on |
| 13 |
> here? |
| 14 |
|
| 15 |
Since there is such a command, is it possible (and worthwhile) to use |
| 16 |
lbzip2 instead of bzip2 with portage? (lbzip2 is ridiculously fast when |
| 17 |
you have the cores and the RAM ...) |
Archives