From: Justin Findlay <justin@jfindlay.us>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gcc problems after dep -d
Date: Sat, 28 Oct 2006 10:45:52 -0600 [thread overview]
Message-ID: <20061028164552.GA19087@archimedes> (raw)
In-Reply-To: <4543257D.2010404@rootsr.com>
On AD 2006 October 28 Saturday 11:40:13 AM +0200, Hans de Hartog wrote:
> checking for C++ compiler default output file name... configure: error:
> C++ compiler cannot create executables
>
> or
>
> gcc-config error: Could not run/locate "gcc"
> ...
> [I--] [ -] sys-devel/gcc-4.1.1 (4.1)
> [I--] [ ] sys-devel/gcc-config-1.3.13-r4 (0)
> [I--] [ ] x11-misc/gccmakedep-1.0.2 (0)
I think there is more going on here than gcc-config. I encountered the
very same problems on my machine only after having done an `emerge -uDN
world` and only having one compiler, gcc-4.4.4-r1, on the system.
Hans, I was able to fix gcc-config with `gcc-config -f 1`. However not
only is /usr/bin/gcc seg faulting but
/usr/x86_64-pc-linux-gnu/gcc-bin/4.1.1/gcc is also insomuch that I can't
even compile this simple program without a segmentation fault,
int main()
{
return 0;
}
yet even after having done `gcc-config -f 1` the profile may be correct
according to gcc-config,
# gcc-config -l
[1] x86_64-pc-linux-gnu-4.1.1 *
but the compiler still gives segmentation faults. This totally baffles
me as `ldd /usr/x86_64-pc-linux-gnu/gcc-bin/4.1.1/gcc` shows that gcc
only links in
libc.so.6 => /lib/libc.so.6 (0x00002aadee5c4000)
/lib64/ld-linux-x86-64.so.2 (0x00002aadee4a6000)
and the mtimes on all three files (gcc, libc.so, ld-linux-x86-64.so)
are according to ls:
lrwxrwxrwx 1 root root 23 Sep 4 22:39 /usr/x86_64-pc-linux-gnu/gcc-bin/4.1.1/gcc -> x86_64-pc-linux-gnu-gcc
-rwxr-xr-x 1 root root 140K Sep 4 22:39 /usr/x86_64-pc-linux-gnu/gcc-bin/4.1.1/x86_64-pc-linux-gnu-gcc
-rwxr-xr-x 1 root root 1.4M Oct 1 22:54 /lib64/libc-2.5.so
lrwxrwxrwx 1 root root 11 Oct 1 22:54 /lib64/libc.so.6 -> libc-2.5.so
-rwxr-xr-x 1 root root 140K Oct 1 22:54 /lib64/ld-2.5.so
lrwxrwxrwx 1 root root 9 Oct 1 22:54 /lib64/ld-linux-x86-64.so.2 -> ld-2.5.so
These files are clearly much older than yesterday which is when I began
having these gcc problems. Unfortunately I'm still stumped and am
without a working gcc in the meantime.
Justin
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2006-10-28 16:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-28 9:40 [gentoo-user] gcc problems after dep -d Hans de Hartog
2006-10-28 11:43 ` Hans de Hartog
2006-10-28 11:50 ` Bo Ørsted Andresen
2006-10-28 12:47 ` Hans de Hartog
2006-10-28 15:04 ` Philip Webb
2006-10-28 15:33 ` Hans de Hartog
2006-10-28 16:19 ` [gentoo-user] " Harm Geerts
2006-10-28 20:01 ` [gentoo-user] " Bo Ørsted Andresen
2006-10-28 20:10 ` Bo Ørsted Andresen
2006-10-29 14:17 ` Hans de Hartog
2006-10-29 14:38 ` Bo Ørsted Andresen
2006-10-29 14:55 ` Hans de Hartog
2006-10-29 10:18 ` Hans de Hartog
2006-10-28 16:45 ` Justin Findlay [this message]
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=20061028164552.GA19087@archimedes \
--to=justin@jfindlay.us \
--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