[gentoo-user] GCC upgrade can't run fix_libtool_files

[gentoo-user] GCC upgrade can't run fix_libtool_files

[Nikos Chantziaras]

Does someone know what causes the error? I got this when upgrading from 
GCC 4.8.2 to 4.8.3:

 >>> Installing (1 of 1) sys-devel/gcc-4.8.3
  * gcc-config: Could not locate 'x86_64-pc-linux-gnu-4.8.2' in 
'/etc/env.d/gcc/' !
  * Running 'fix_libtool_files.sh 4.8.2'
  * Scanning libtool files for hardcoded gcc library paths...
  * gcc-config: Active gcc profile is invalid!
gcc-config: error: could not run/locate 'gcc'
:0: assertion failed: (gcc -dumpversion) | getline NEWVER)

Re: [gentoo-user] GCC upgrade can't run fix_libtool_files

[Daniel Frey]

On 06/16/2014 09:56 AM, Nikos Chantziaras wrote:
> Does someone know what causes the error? I got this when upgrading from
> GCC 4.8.2 to 4.8.3:
> 
>>>> Installing (1 of 1) sys-devel/gcc-4.8.3
>  * gcc-config: Could not locate 'x86_64-pc-linux-gnu-4.8.2' in
> '/etc/env.d/gcc/' !
>  * Running 'fix_libtool_files.sh 4.8.2'
>  * Scanning libtool files for hardcoded gcc library paths...
>  * gcc-config: Active gcc profile is invalid!
> gcc-config: error: could not run/locate 'gcc'
> :0: assertion failed: (gcc -dumpversion) | getline NEWVER)
> 
> 

It looks like you've upgraded gcc and removed the version that was
currently active.

What's the output of `gcc-config -l`?

It should look something like this:
$ sudo gcc-config -l
 [1] x86_64-pc-linux-gnu-4.7.3 *


The asterisk means it's active. If you see a list and none are active,
you need to set one.

Dan

[gentoo-user] Re: GCC upgrade can't run fix_libtool_files

[Nikos Chantziaras]

On 16/06/14 20:02, Daniel Frey wrote:
> On 06/16/2014 09:56 AM, Nikos Chantziaras wrote:
>> Does someone know what causes the error? I got this when upgrading from
>> GCC 4.8.2 to 4.8.3:
>>
>>>>> Installing (1 of 1) sys-devel/gcc-4.8.3
>>   * gcc-config: Could not locate 'x86_64-pc-linux-gnu-4.8.2' in
>> '/etc/env.d/gcc/' !
>>   * Running 'fix_libtool_files.sh 4.8.2'
>>   * Scanning libtool files for hardcoded gcc library paths...
>>   * gcc-config: Active gcc profile is invalid!
>> gcc-config: error: could not run/locate 'gcc'
>> :0: assertion failed: (gcc -dumpversion) | getline NEWVER)
>>
>
> It looks like you've upgraded gcc and removed the version that was
> currently active.
>
> What's the output of `gcc-config -l`?
>
> It should look something like this:
> $ sudo gcc-config -l
>   [1] x86_64-pc-linux-gnu-4.7.3 *
>
>
> The asterisk means it's active. If you see a list and none are active,
> you need to set one.

I was only interested in the fix_libtool_files.sh error. The gcc-config 
error is probably due to portage removing 4.8.2 when updating to 4.8.3, 
since it's a minor version update.