| 1 |
On 30/12/2016 11:44, Nikos Chantziaras wrote: |
| 2 |
> A world update emerged gcc-5.4.0-r2 (update from 5.4.0). At the end of |
| 3 |
> the build, I got this: |
| 4 |
> |
| 5 |
> * Python seems to be broken, attempting to locate CHOST ourselves ... |
| 6 |
> * Switching native-compiler to x86_64-pc-linux-gnu-5.4.0 |
| 7 |
> ...PORTAGE_BZIP2_COMMAND setting is invalid: 'bzip2' |
| 8 |
> PORTAGE_BZIP2_COMMAND setting from make.globals is invalid: 'bzip2' |
| 9 |
> |
| 10 |
> I'm not seeing how python is broken here (works fine), and why |
| 11 |
> PORTAGE_BZIP2_COMMAND is invalid. Can someone explain what's going on here? |
| 12 |
> |
| 13 |
> |
| 14 |
|
| 15 |
|
| 16 |
I get the same odd message for all of the 5.x series for which I have |
| 17 |
build logs: |
| 18 |
|
| 19 |
$ grep -r "Python seems to be broken" /var/log/portage/ |
| 20 |
/var/log/portage/sys-devel:gcc-5.3.0:20161009-190108.log: * Python seems |
| 21 |
to be broken, attempting to locate CHOST ourselves ... |
| 22 |
/var/log/portage/sys-devel:gcc-5.4.0-r2:20161229-080856.log: * Python |
| 23 |
seems to be broken, attempting to locate CHOST ourselves ... |
| 24 |
/var/log/portage/sys-devel:gcc-5.4.0:20161009-182055.log: * Python seems |
| 25 |
to be broken, attempting to locate CHOST ourselves ... |
| 26 |
|
| 27 |
The 4.x series is fine. |
| 28 |
|
| 29 |
I suggest file a bug |
| 30 |
|
| 31 |
-- |
| 32 |
Alan McKinnon |
| 33 |
alan.mckinnon@×××××.com |
Archives