From: Jeff Donsbach <jeff_donsbach@yahoo.com>
To: gentoo-alpha@lists.gentoo.org
Subject: [gentoo-alpha] problem upgrading the toolchain
Date: Tue, 6 Dec 2005 06:27:45 -0800 (PST) [thread overview]
Message-ID: <20051206142745.48983.qmail@web32913.mail.mud.yahoo.com> (raw)
Hi folks,
I'm trying to get Gentoo installed on a new (to me)
Miata. I got the base system installed and got
upgraded to the 2.6.14.2 kernel. Looks good so far. By
the way, the 2005.1 LiveCD wouldn't boot on this
system with the default 2.6 kernel either. I had to
boot the 2.4 kernel and install that way, then upgrade
to the 2.6 kernel. But, that isn't my current problem.
I'm having trouble updating the tool chain. GLIBC
seems to have rebuilt fine with NPTL support. As an
example, here is the log file when trying to emerge
binutils -
=======
alpha1 build # more config.log
This file contains any messages produced by compilers
while
running configure, to aid debugging if configure makes
a mistake.
configure:595: checking host system type
configure:616: checking target system type
configure:634: checking build system type
configure:689: checking for a BSD compatible install
configure:742: checking whether ln works
configure:766: checking whether ln -s works
configure:1779: checking for gcc
configure:1892: checking whether the C compiler
(/usr/bin/gcc -mieee -mcpu=ev56 -pipe -O2 ) works
configure:1908: /usr/bin/gcc -o conftest -mieee
-mcpu=ev56 -pipe -O2 conftest.c 1>&5
gcc: Internal error: Segmentation fault (program as)
Please submit a full bug report.
See <URL:http://bugs.gentoo.org/> for instructions.
configure: failed program was:
#line 1903 "configure"
#include "confdefs.h"
main(){return(0);}
=====
Now, the strange part is, if I make a conftest.c with
the two lines above and manually run "usr/bin/gcc -o
conftest -mieee -mcpu=ev56 -pipe -O2 conftest.c" ,
it works just fine!
Any idea what could be wrong? Other ebuilds seem to
fail the same way. Oh, my gcc version is:
alpha1 build # gcc --version
gcc (GCC) 3.3.2 20040119 (Gentoo Linux 3.3.2-r7,
propolice-3.3-7)
My glibc version is 2.3.5-r3 with NPTL support in my
USE flags.
Thanks,
Jeff D
__________________________________________
Yahoo! DSL Something to write home about.
Just $16.99/mo. or less.
dsl.yahoo.com
--
gentoo-alpha@gentoo.org mailing list
next reply other threads:[~2005-12-06 14:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 14:27 Jeff Donsbach [this message]
2005-12-06 17:02 ` [gentoo-alpha] problem upgrading the toolchain Nils o. Janus
2005-12-06 18:45 ` Jeff Donsbach
2005-12-06 19:54 ` Marc Giger
2005-12-07 3:39 ` Jeff Donsbach
2005-12-07 10:20 ` Bryan Østergaard
2005-12-07 17:48 ` Marc Giger
2005-12-07 18:15 ` Marc Giger
2005-12-09 20:33 ` Marc Giger
2005-12-14 7:00 ` [gentoo-alpha] more problems... nptl releated also? Jeff Donsbach
2005-12-07 14:38 ` [gentoo-alpha] problem upgrading the toolchain Jeff Donsbach
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=20051206142745.48983.qmail@web32913.mail.mud.yahoo.com \
--to=jeff_donsbach@yahoo.com \
--cc=gentoo-alpha@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