From: "Brian Webb" <webbb@desertscenes.net>
To: <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Re: GCC3.1 bootstrap fails
Date: Sun, 2 Jun 2002 20:52:38 -0700 (MST) [thread overview]
Message-ID: <36664.192.168.0.6.1023076358.squirrel@web.local> (raw)
In-Reply-To: <200206022332.09275.verwilst@gentoo.org>
I tried the 1.3-gcc3.1 profile but ran into some problems, and now I can't
get any 3.0 profile to work!
I first booted from a 1.1a stage1 CD, I then downloaded an untared the
1.3-gcc3.1 stage1, changed the CFLAGS and CXXFLAGS in make.conf to
"-march=athlon-xp -O3 -pipe", and bootstrapped.
I soon realized that make.profile was pointing to the default profile when
it started building gcc-2.95.3. Since this is a 3.1 bootstrap, it seems
like the default make.profile link should be to the 3.0 profile instead,
but that wasn't a problem. I started over, remembering to change the
make.profile link, and bootstrap finished successfully.
There were some errors about info files (this was mentioned in a previous
email), but I didn't think much of them. Unfortunately, the "emerge
system" step failed when building e2fsprogs because it couldn't find
makeinfo.
While I was trying to figure out how to build makeinfo I decided to
"emerge rsync" just in case something had gotten fixed in the last couple
of hours ;-). That's when things really fell apart. After that I
couldn't get any emerges to work. I kept getting "Couldn't find match
for..." from emerge.
At this point I decided that something was really messed up, so decided to
start over from a more standard gcc-3.1 bootstrap that worked for me just
a day or two ago.
I have successfully bootstrapped on a similar system using a 1.1a stage1
and the 3.0 make profile as long as I don't change the CFLAGS or CXXFLAGS
until the "emerge system" step (after the gcc 3.1 compiler has been
built). Unfortunately, this is no longer working either.
I now get the "Couldn't find match for..." error messages almost
immediately after running bootstrap.sh. The error messages start just
after portage has been emerged. Has something recently changed with
portage or the gcc 3.0 profile that could have caused this? Any idea how
I can fix this?
Brian
> Would be cool if you could try and bootstrap again with
> -fomit-frame-pointer, and now use the 1.3-gcc3.1 tarball from ibiblio
> (http://www.ibiblio.org/gentoo/releases/build/) i just made. If it
> fails, i guess we should filter out most of the optimisations... I
> think the new gcc3.1-compiled tarball will make all the gcc3.1-users
> much happier :o) I also updated the packages file from the gcc 3.1
> profile, and the make.defaults. Please keep us posted on any progress!
next prev parent reply other threads:[~2002-06-03 3:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020602170104.750B0AC465@chiba.3jane.net>
2002-06-02 17:42 ` [gentoo-dev] Re: GCC3.1 bootstrap fails Prashanth Aditya Susarla
2002-06-02 21:32 ` Bart Verwilst
2002-06-03 0:53 ` Prashanth Aditya Susarla
2002-06-03 1:18 ` Prashanth Aditya Susarla
2002-06-03 2:07 ` Prashanth Aditya Susarla
2002-06-03 3:52 ` Brian Webb [this message]
2002-06-03 6:04 ` Brian Webb
2002-06-03 5:59 ` Prashanth Aditya Susarla
2002-06-03 6:08 ` [gentoo-dev] Re: Correction - " Prashanth Aditya Susarla
2002-06-04 17:12 ` [gentoo-dev] " Matthew Kennedy
2002-06-03 16:49 ` Prashanth Aditya Susarla
2002-06-05 5:51 ` Christian Hergl
2002-06-04 6:05 ` Prashanth Aditya Susarla
2002-06-04 17:13 Zaborowski, Ed, Ctr, AFPCA/OAC
2002-06-03 16:57 ` Prashanth Aditya Susarla
-- strict thread matches above, loose matches on Subject: below --
2002-06-04 19:07 Zaborowski, Ed, Ctr, AFPCA/OAC
2002-06-03 18:42 ` Prashanth Aditya Susarla
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=36664.192.168.0.6.1023076358.squirrel@web.local \
--to=webbb@desertscenes.net \
--cc=gentoo-dev@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