public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Richard Fish" <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Remerge the system with gcc-4.1?
Date: Fri, 8 Sep 2006 12:49:32 -0700	[thread overview]
Message-ID: <7573e9640609081249i59272a88md73c276e52498833@mail.gmail.com> (raw)
In-Reply-To: <49bf44f10609080724m2678c3dbw1f08d6bf265b9ce8@mail.gmail.com>

On 9/8/06, Grant <emailgrant@gmail.com> wrote:
> I've followed the GCC upgrade guide before without problems, but now
> I'm scared.  Is all the trouble because of how Gentoo works or how GCC
> works?  What is the trouble like?  Packages that won't compile, or
> different things breaking in the system?

There are a few classes of problems here:

1. Packages failing to build with gcc-4.1.  Usually the ~arch version
of that package will build fine, so you may need to accept ~arch
keywords for some packages in package.keywords.  This is by far the
most common and serious issue.

2. C++ ABI issues.  While the system is in the process of being
rebuilt, you can have some C++ programs using a different ABI than the
libraries they link to, or the libraries can have conflicting ABIs.
This should not be a problem once the emerge -e world completes, but
can make it difficult to use the system while this is happening.

3. Problems with other packages being blamed on the gcc upgrade.  FEX
glibc-2.4 is now nptl only, and will no longer work in i386 hosts
(must be i586 or better), and probably conflicts with no-nptl
profiles, etc.

You might want to take a look at the tracker bugs:

http://bugs.gentoo.org/show_bug.cgi?id=140707
http://bugs.gentoo.org/show_bug.cgi?id=117482

-Richard
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2006-09-08 19:56 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49bf44f10609072007w4c110d77je1152ea578c7e708@mail.gmail.com>
2006-09-08  6:16 ` [gentoo-user] Remerge the system with gcc-4.1? Erik
2006-09-08  6:26   ` Boris Fersing
2006-09-08  7:09     ` jarry
2006-09-08 11:56       ` Timothy A. Holmes
2006-09-08 12:24         ` Dale
2006-09-08 13:11           ` Jean-Marc Beaune
2006-09-08 15:44             ` michael
2006-09-11 15:58               ` Matthias Bethke
2006-09-08 14:24         ` Grant
2006-09-08 14:33           ` Michael Crute
2006-09-09  0:40             ` Mark Kirkwood
2006-09-08 14:37           ` Andrew Gaydenko
2006-09-08 14:59             ` Neil Bothwick
2006-09-08 15:26               ` Andrew Gaydenko
2006-09-08 16:05                 ` Neil Bothwick
2006-09-08 16:18                   ` Andrew Gaydenko
2006-09-08 15:12           ` Timothy A. Holmes
2006-09-08 15:30             ` Jean-Marc Beaune
2006-09-08 15:45               ` michael
2006-09-08 17:02             ` Bo Ørsted Andresen
2006-09-08 17:09               ` Timothy A. Holmes
2006-09-08 17:35                 ` Bo Ørsted Andresen
2006-09-08 18:07                   ` Timothy A. Holmes
2006-09-08 19:05                     ` Bo Ørsted Andresen
2006-09-08 19:49           ` Richard Fish [this message]
2006-09-08 20:10             ` Timothy A. Holmes
2006-09-08 20:29               ` Richard Fish
2006-09-08  7:22   ` Richard Fish
2006-09-08 21:34     ` [gentoo-user] " Peter
2006-09-08 22:12       ` Richard Fish
2006-09-08 22:20         ` Peter
2007-10-10  5:39         ` Daevid Vincent
2007-10-10  5:51           ` Mark Kirkwood
2007-10-10 22:32           ` Mick
2006-09-08 21:35     ` Peter
2006-09-08  6:23 ` [gentoo-user] " Dirk Heinrichs

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=7573e9640609081249i59272a88md73c276e52498833@mail.gmail.com \
    --to=bigfish@asmallpond.org \
    --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