| 1 |
2009/11/5 Volker Armin Hemmann <volkerarmin@××××××××××.com>: |
| 2 |
> On Donnerstag 05 November 2009, Steve wrote: |
| 3 |
> |
| 4 |
> |
| 5 |
>> checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc |
| 6 |
>> checking for C compiler default output... configure: error: C compiler |
| 7 |
>> cannot create executables |
| 8 |
>> check `config.log' for details. |
| 9 |
> |
| 10 |
>> I presume that this is a profile issue - but I'm unclear what the fault |
| 11 |
>> might be... I'm reluctant to continue hacking as, I suspect, I'm more |
| 12 |
>> likely to break things than stumble across an appropriate fix. |
| 13 |
>> |
| 14 |
>> Can anyone tell me why emerge is having such a problem with my compiler |
| 15 |
>> - and, hopefully, ideally, how best to resolve this? |
| 16 |
>> |
| 17 |
> |
| 18 |
> yes, don't use locate. Also check the symlinks. Reset them with eselect gcc if |
| 19 |
> you have to. |
| 20 |
> |
| 21 |
> Then try all your emerges with --tree you get a lot more helpfull output. |
| 22 |
> Also, when a dependency is missing revdep-rebuilt loves to fail. You can hunt |
| 23 |
> that down with --tree or just re--emerging the stuff. |
| 24 |
|
| 25 |
If you removed gcc for some reason in your depclean largesse you may |
| 26 |
need to use a LiveCD or restore the binary from a backup - I'm sure |
| 27 |
that this has been raised before in this M/L but I am not sure how |
| 28 |
hard it may be to find the thread. Hopefully, one of the gurus will |
| 29 |
chime in on how to go about recovering your system. |
| 30 |
-- |
| 31 |
Regards, |
| 32 |
Mick |
Archives