public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] can not compile / emerge
Date: Tue, 9 Sep 2014 22:38:18 +0100	[thread overview]
Message-ID: <201409092238.19670.michaelkintzios@gmail.com> (raw)
In-Reply-To: <20140909191509.GG23438@syscon7>

[-- Attachment #1: Type: Text/Plain, Size: 1140 bytes --]

On Tuesday 09 Sep 2014 20:15:09 Joseph wrote:
> On 09/09/14 14:46, Todd Goodman wrote:
> >* Joseph <syscon780@gmail.com> [140909 14:37]:
> >> I was installing an application gimp and all of a sudden I got an error:
> >[SNIP]
> >
> >> configure: error: in
> >> `/var/tmp/portage/media-gfx/gimp-2.8.10-r1/work/gimp-2.8.10':
> >> configure: error: C compiler cannot create executables
> >> See `config.log' for more details
> >
> >What does 'gcc-config -l' show?
> 
> I tried to set blindly gcc to active one: "gcc-config 1" but I get the same
> error
> 
>  * gcc-config: Could not get portage CHOST!
>  * gcc-config: You should verify that CHOST is set in one of these places:
>  * gcc-config:  - //etc/portage/make.conf
>  * gcc-config:  - active environment
> 
> It is a new installation on SSD and it is broken.
> I can't proceed with gcc upgrade/setting, in fact my system is currently
> broken.

You do not have an /etc/portage/make.conf file, or you have not configured the 
default with the correct settings?

Follow the installation guide and you should find your way out of there.

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2014-09-09 21:38 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-09 18:36 [gentoo-user] can not compile / emerge Joseph
2014-09-09 18:45 ` Joseph
2014-09-09 18:46 ` Todd Goodman
2014-09-09 19:02   ` Joseph
2014-09-09 19:15   ` Joseph
2014-09-09 21:38     ` Mick [this message]
2014-09-09 21:57       ` Joseph
2014-09-09 22:20         ` Neil Bothwick
2014-09-09 22:49           ` Joseph
2014-09-10  3:29       ` Kerin Millar
2014-09-09 18:49 ` Dale
2014-09-10  2:59 ` Kerin Millar
2014-09-10  3:21   ` Joseph
2014-09-10  3:27     ` Kerin Millar
2014-09-10  3:50       ` [gentoo-user] [SOLVED] " Joseph
2014-09-10  3:57         ` Kerin Millar
2014-09-10  4:16           ` Joseph
2014-09-10  5:01             ` Kerin Millar
2014-09-10  5:10               ` Kerin Millar
2014-09-10  5:32                 ` [gentoo-user] BACKUPS Joseph
2014-09-10  7:14                   ` Alan McKinnon
2014-09-10  7:47                     ` Dale
2014-09-10  7:51                       ` J. Roeleveld
2014-09-10  8:03                         ` Dale
2014-09-10  9:13                           ` Alan McKinnon
2014-09-10  8:34                     ` Neil Bothwick
2014-09-10 11:03                   ` Kerin Millar
2014-09-10  5:20               ` [gentoo-user] [SOLVED] can not compile / emerge Joseph
2014-09-11 12:07             ` [gentoo-user] " James
2014-09-11 12:28               ` Joseph
2014-09-11 13:36                 ` J. Roeleveld
2014-09-12 17:09                   ` Joseph
2014-09-11 13:40                 ` James

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201409092238.19670.michaelkintzios@gmail.com \
    --to=michaelkintzios@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox