public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Spider <spider@gentoo.org>
To: gentoo-dev <gentoo-dev@gentoo.org>
Subject: [gentoo-dev] gcc 3.1 inconsistencies :
Date: Wed, 5 Jun 2002 03:23:51 +0200	[thread overview]
Message-ID: <20020605032351.4194bfa6.spider@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1315 bytes --]

Hello, I did a new gcc3.1 bootstrap when I was forced offline, and
theese are my notes:


bootstrap went nice first time, but I managed to abort it and mess up a
few times, generally my fault to set the wrong flags (1.3 gcc 3.1 image)

Texinfo needs to be fixed and unmasked for the gcc3 profile (it doesn't
break any old system so it should work nicely)

have gcc 2.95.3 hide it , gcc 3.1 depend on it... works nice :)

after a time of recompiling system with new flags I noted some ncurses
stuff started to break... couldn't compile gpm, zsh, cscope and other
things, was odded by this until I checked ncurses (clean new install )
with gcc 3.1's headers... 

xfree has some problems with a source not found for the latest masked
verison


Wonderfully enough, this was solved by recompiling -gcc- ..... 
fixincludes script did something there I suspect.

unmask gnome2 and emerge gnome works. (not a single breakage!! )
gdm works perfect once Xfree was started. 

Generally the whole progress felt really smooth. I'm still recovering
and hope my connection will last through this.

soo, right now I'm running march=athlon-tbird -O3 -pipe for most things
:)


//Spider

--
begin  .signature
This is a .signature virus! Please copy me into your .signature!
See Microsoft KB Article Q265230 for more information.
end

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2002-06-05  1:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-05  1:23 Spider [this message]
2002-06-05  3:22 ` [gentoo-dev] gcc 3.1 inconsistencies : Dave Lee
2002-06-05  5:00 ` fthieme

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=20020605032351.4194bfa6.spider@gentoo.org \
    --to=spider@gentoo.org \
    --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