| 1 |
On 16/06/14 20:02, Daniel Frey wrote: |
| 2 |
> On 06/16/2014 09:56 AM, Nikos Chantziaras wrote: |
| 3 |
>> Does someone know what causes the error? I got this when upgrading from |
| 4 |
>> GCC 4.8.2 to 4.8.3: |
| 5 |
>> |
| 6 |
>>>>> Installing (1 of 1) sys-devel/gcc-4.8.3 |
| 7 |
>> * gcc-config: Could not locate 'x86_64-pc-linux-gnu-4.8.2' in |
| 8 |
>> '/etc/env.d/gcc/' ! |
| 9 |
>> * Running 'fix_libtool_files.sh 4.8.2' |
| 10 |
>> * Scanning libtool files for hardcoded gcc library paths... |
| 11 |
>> * gcc-config: Active gcc profile is invalid! |
| 12 |
>> gcc-config: error: could not run/locate 'gcc' |
| 13 |
>> :0: assertion failed: (gcc -dumpversion) | getline NEWVER) |
| 14 |
>> |
| 15 |
> |
| 16 |
> It looks like you've upgraded gcc and removed the version that was |
| 17 |
> currently active. |
| 18 |
> |
| 19 |
> What's the output of `gcc-config -l`? |
| 20 |
> |
| 21 |
> It should look something like this: |
| 22 |
> $ sudo gcc-config -l |
| 23 |
> [1] x86_64-pc-linux-gnu-4.7.3 * |
| 24 |
> |
| 25 |
> |
| 26 |
> The asterisk means it's active. If you see a list and none are active, |
| 27 |
> you need to set one. |
| 28 |
|
| 29 |
I was only interested in the fix_libtool_files.sh error. The gcc-config |
| 30 |
error is probably due to portage removing 4.8.2 when updating to 4.8.3, |
| 31 |
since it's a minor version update. |
Archives