public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "brullo nulla" <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 16:10:56 +0100	[thread overview]
Message-ID: <93ae19410701190710k39b5aea4s59d40b016c202d35@mail.gmail.com> (raw)
In-Reply-To: <200701191210.45109.alan@linuxholdings.co.za>

> Dunno about gcc-4.2, you'll have to look at the gnu roadmap to get a
> hint of when they think it'll move closer to a release

OK.

> Not at all necessary. The kernel is a free standing block of C code and
> depends only on itself, so ABI issues with other apps simply don;t
> happen. As long as the kernel and all it's modules were compiled with
> the same compiler you will always be fine. (There are exceptions of
> course but with that rule of thumb you can't go wrong)

Yes, but if I keep my 3.4.x compiled kernel and I recompile modules in
Portage with 4.1, there will be problems, maybe (for example, the
vmmon module of vmware-player). Well, I think I'll recompile. I have
other reasons to do it.

> Make sure any kernel modules you may have that are not in portage also
> get recompiled.

Sure (I shouldn't have). I guess also programs not in portage will
have to be recompiled.

Thanks again,
m.
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-01-19 15:16 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.
2007-01-19  0:09     ` Dan Farrell
2007-01-19 10:10 ` Alan McKinnon
2007-01-19 15:10   ` brullo nulla [this message]
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=93ae19410701190710k39b5aea4s59d40b016c202d35@mail.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