1 |
On 09/09/2014 22:38, Mick wrote: |
2 |
> On Tuesday 09 Sep 2014 20:15:09 Joseph wrote: |
3 |
>> On 09/09/14 14:46, Todd Goodman wrote: |
4 |
>>> * Joseph <syscon780@×××××.com> [140909 14:37]: |
5 |
>>>> I was installing an application gimp and all of a sudden I got an error: |
6 |
>>> [SNIP] |
7 |
>>> |
8 |
>>>> configure: error: in |
9 |
>>>> `/var/tmp/portage/media-gfx/gimp-2.8.10-r1/work/gimp-2.8.10': |
10 |
>>>> configure: error: C compiler cannot create executables |
11 |
>>>> See `config.log' for more details |
12 |
>>> |
13 |
>>> What does 'gcc-config -l' show? |
14 |
>> |
15 |
>> I tried to set blindly gcc to active one: "gcc-config 1" but I get the same |
16 |
>> error |
17 |
>> |
18 |
>> * gcc-config: Could not get portage CHOST! |
19 |
>> * gcc-config: You should verify that CHOST is set in one of these places: |
20 |
>> * gcc-config: - //etc/portage/make.conf |
21 |
>> * gcc-config: - active environment |
22 |
>> |
23 |
>> It is a new installation on SSD and it is broken. |
24 |
>> I can't proceed with gcc upgrade/setting, in fact my system is currently |
25 |
>> broken. |
26 |
> |
27 |
> You do not have an /etc/portage/make.conf file, or you have not configured the |
28 |
> default with the correct settings? |
29 |
|
30 |
This is not pertinent to the matter at hand. Even if make.conf cannot be |
31 |
sourced, CHOST will be sourced from the profile and portage is perfectly |
32 |
capable of functioning. |
33 |
|
34 |
There is no need for a user to define CHOST. At best, it is a no-op and, |
35 |
at worst, the user may screw up and define it in such a way that it is |
36 |
at odds with the profile. |
37 |
|
38 |
The error message from gcc-config isn't particularly helpful because it |
39 |
falsely implies that make.conf or the "active environment" - as opposed |
40 |
to portage's environment - are the only valid sources. |
41 |
|
42 |
--Kerin |