Re: [gentoo-user] Weird warning message when emerging gcc

2016-12-31 Thread Daniel Frey
On 12/31/2016 06:59 AM, Håkon Alstadheim wrote: > > > Den 30. des. 2016 14:44, skrev lee: >> Nikos Chantziaras 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

Re: [gentoo-user] Weird warning message when emerging gcc

2016-12-31 Thread Håkon Alstadheim
Den 30. des. 2016 14:44, skrev lee: > Nikos Chantziaras 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

Re: [gentoo-user] Weird warning message when emerging gcc

2016-12-30 Thread lee
Nikos Chantziaras 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 >

Re: [gentoo-user] Weird warning message when emerging gcc

2016-12-30 Thread Miroslav Rovis
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

Re: [gentoo-user] Weird warning message when emerging gcc

2016-12-30 Thread Alan McKinnon
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 >

[gentoo-user] Weird warning message when emerging gcc

2016-12-30 Thread Nikos Chantziaras
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'