public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <peter@humphrey.ukfsn.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Can't emerge sandbox
Date: Mon, 10 Nov 2008 09:35:27 +0000	[thread overview]
Message-ID: <200811100935.27608.peter@humphrey.ukfsn.org> (raw)
In-Reply-To: <tkrat.499b5d7a74195d35@igpm.rwth-aachen.de>

On Thursday 06 November 2008 18:42:44 Helmut Jarausch wrote:

> The lines
> configure:2292: i686-pc-linux-gnu-gcc -march=opteron -O2 -pipe  
> conftest.c  >&5 /usr/libexec/gcc/i686-pc-linux-gnu/ld: crt1.o: No such
> file: No such file or directory collect2: ld returned 1 exit status
>
> look like a misconfigured gcc.

That was it.

> Can you emerge any package which requires the C-compiler?
> Try
> gcc-config -l

$ gcc-config -l
 [1] i686-pc-linux-gnu-4.2.2 *

 [2] x86_64-pc-linux-gnu-4.1.2 *

$ qfile i686-pc-linux-gnu-4.2.2
cross-i686-pc-linux-gnu/gcc (/etc/env.d/gcc/i686-pc-linux-gnu-4.2.2)

I did have the cross-compiler stuff installed when I was experimenting with 
distcc, but I removed it long ago. Looks like something hung on.

A simple emerge -C cross-i686-pc-linux-gnu/gcc corrected the problem, as 
now:

$ gcc-config -l
 [1] x86_64-pc-linux-gnu-4.1.2 *

...and emerge -q1 sandbox runs to completion. I still don't know though why 
only sandbox was affected - 21 other packages were merged ok.

> I hope this helps,

Certainly did - thanks. Now to figure out how to resume the emerge -e world 
from where it stopped :-)

Thanks also to the others who offered help.

-- 
Rgds
Peter



  reply	other threads:[~2008-11-10  9:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-06 18:02 [gentoo-user] Can't emerge sandbox Peter Humphrey
2008-11-06 18:42 ` Helmut Jarausch
2008-11-10  9:35   ` Peter Humphrey [this message]
2008-11-10  9:58     ` Neil Bothwick
2008-11-07  8:16 ` Mick
2008-11-07 19:42 ` Jorge Peixoto de Morais Neto

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=200811100935.27608.peter@humphrey.ukfsn.org \
    --to=peter@humphrey.ukfsn.org \
    --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