From: "b.n." <brullonulla@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] gcc 3.4.x --> 4.1.x : a couple of questions
Date: Thu, 18 Jan 2007 22:24:06 +0000 [thread overview]
Message-ID: <45AFF386.1060404@gmail.com> (raw)
Hi,
Quite late :), I'm going to do my homework, that is the loooong upgrade
to gcc 3.4.x --> 4.1.x
The subject has been widely discussed, so I've just a couple of
questions to be super-safe:
- I'm going to follow [1] (of course) and [2] (looks nice). Other useful
guides?
- Is there a new incompatible GCC upgrade going to be unmasked? I see
4.2 and 4.3 are hard masked, but if there is the suspicion they're going
to be used relatively soon AND they are not binary compatible with 4.1,
I may wait for those. When I did 3.3-->3.4, I waited long, and 4.1
became stable after a week... :/
- Is it mandatory/highly advisable to recompile also the kernel, or can
I postpone? In the first case, when it's better to recompile it (before
all/after all)?
- Do I have to emerge glibc 2.4 first and gcc later, or I can have glibc
emerged in the emerge -e system?
- Any other glitch/tarpit I must be aware of?
[1]http://www.gentoo.org/doc/en/gcc-upgrading.xml#doc_chap2
[2]http://www.benr75.com/pages/gentoo_gcc_4.1.1_upgrade_guide
Thanks for all!
m.
--
gentoo-user@gentoo.org mailing list
next reply other threads:[~2007-01-18 21:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 22:24 b.n. [this message]
2007-01-18 22:19 ` [gentoo-user] gcc 3.4.x --> 4.1.x : a couple of questions Bo Ørsted Andresen
2007-01-19 0:20 ` b.n.
2007-01-19 0:09 ` Dan Farrell
2007-01-19 10:10 ` Alan McKinnon
2007-01-19 15:10 ` brullo nulla
2007-01-19 15:50 ` Alan McKinnon
2007-01-19 16:47 ` brullo nulla
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=45AFF386.1060404@gmail.com \
--to=brullonulla@gmail.com \
--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