From: "b.n." <brullonulla@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gcc 3.4.x --> 4.1.x : a couple of questions
Date: Fri, 19 Jan 2007 00:20:57 +0000 [thread overview]
Message-ID: <45B00EE9.80705@gmail.com> (raw)
In-Reply-To: <200701182319.06111.bo.andresen@zlin.dk>
Bo Ørsted Andresen ha scritto:
> On Thursday 18 January 2007 23:24, b.n. wrote:
>> - I'm going to follow [1] (of course) and [2] (looks nice). Other useful
>> guides?
>
> [1] alone should be fine. Assuming your CHOST isn't i386.
Sorry for lack of info. I'm running x86 stable, chost is i686-pc-linux-gnu
> You didn't tell us whether you are running stable or ~arch. If you're stable
> then certainly not since it's not even ~arch yet. Even if ~arch I don't think
> so.
OK, perfect.
>> - 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)?
>
> It's best to do it. I think I'd compile it right before `emerge -e world` and
> wait with the reboot till it's all done. That way kernel modules compiled
> during world will be built against a kernel that was compiled with the same
> compiler.
This makes much sense.
So:
emerge -e system
[kernel recompile dance]
[reboot]
emerge -e world
?
>> - Do I have to emerge glibc 2.4 first and gcc later, or I can have glibc
>> emerged in the emerge -e system?
>
> Assuming your CHOST isn't i386 it's fine to just let `emerge -e system` do it
> when instructed to do that.
Ok, thanks.
m.
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-01-18 23:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 22:24 [gentoo-user] gcc 3.4.x --> 4.1.x : a couple of questions b.n.
2007-01-18 22:19 ` Bo Ørsted Andresen
2007-01-19 0:20 ` b.n. [this message]
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=45B00EE9.80705@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