xarchiveshash:a97b736415e990b9d4c8ed760b6c121e

* Re: [gentoo-dev] Re: GCC3.1 bootstrap fails
  @ 2002-06-03  6:04 99%     ` Brian Webb
  0 siblings, 0 replies; 1+ results
From: Brian Webb @ 2002-06-03  6:04 UTC (permalink / raw
  To: gentoo-dev

I think I may have found at least part of the problem.  I noticed that on
my other gcc-3.0 profile machines, texinfo couldn't be emerged.  It turns
out that texinfo is masked.  Texinfo is a required system package in the
gcc-3.0 profile and it's masked the package.mask, which obviously is not a
good thing.  If I unmask texinfo my existing systems are happy, but I
haven't tested it on a bootstrap yet.

Brian

P.S. Sorry about the run-on emails.  I really have to figure out why
Squirrelmail is running all my paragraphs together!!!!

> 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!
>
>
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev

^ permalink raw reply	[relevance 99%]