From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Multiple Update Issues - what order should things be done?
Date: Fri, 5 Mar 2010 21:20:01 +0200 [thread overview]
Message-ID: <201003052120.01622.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <4B9156ED.1050407@libertytrek.org>
On Friday 05 March 2010 21:09:33 Tanstaafl wrote:
> Hello,
>
> I've got a concern with some updates that I need to get done. I'm sorry
> to say I put a few things off a bit too long, and now I'm uncertain as
> to what I should do first, or if it even matters.
>
> Here are the issues:
>
> 1. I'm on an older kernel (gentoo-sources, 2.6.23-r9)
>
> For reasons I won't go into now, the boss would rather wait on updating
> this, but he said if we have to, we have to...
>
> 2. I've currently got the lvm2 update blocker problem due to the
> device-mapper being merged into lvm2. I know how to fix this (according
> to the bug I found):
>
> emerge -C device-mapper && emerge -vuDN lvm2
>
> (/ is not on lvm2, but /usr and /var are)
>
> but...
>
> 3. For some reason mysql wants to be rebuilt, and when I tried, it
> failed saying that it now requires gcc-4.3.4...
>
> I had already installed gcc-4.3.4 a while back, but still haven't
> switched to it, so currently everything is compiled with 4.1.2.
Then switch to 4.3.4
> So, what should I do first? Will the new version of lvm2 work ok with
> the older kernel?
Dunno, what does the ebuild say?
> If so I could switch to gcc-4.3.4, fix/update lvm2,
> then rebuild world, then update the kernel later once the boss is ok
> with it?
Just update the kernel and be done with it. This is the thing to do first and
you already know that. So just do it.
> Also - when you switch compilers, do you need to reboot right away
> (after rebuilding world (and thus the kernel)?
What does rebooting have to do with the compiler? The compiler only builds
code then stops. Rebooting does nothing to it.
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2010-03-05 19:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 19:09 [gentoo-user] Multiple Update Issues - what order should things be done? Tanstaafl
2010-03-05 19:20 ` Alan McKinnon [this message]
2010-03-05 20:40 ` Sebastian Beßler
2010-03-05 23:30 ` Tanstaafl
2010-03-06 6:53 ` Alan McKinnon
2010-03-06 18:39 ` Tanstaafl
2010-03-07 18:17 ` Alan McKinnon
2010-03-07 23:54 ` Dale
2010-03-08 0:55 ` Neil Bothwick
2010-03-08 1:10 ` Dale
2010-03-08 12:44 ` Tanstaafl
2010-03-08 13:05 ` Alan McKinnon
2010-03-08 18:25 ` Tanstaafl
2010-03-08 18:32 ` Mark Knecht
2010-03-08 19:45 ` Neil Walker
2010-03-08 20:10 ` Alan McKinnon
2010-03-08 20:39 ` Dale
2010-03-08 20:55 ` Alan McKinnon
2010-03-08 22:39 ` Dale
2010-03-08 20:53 ` Neil Bothwick
2010-03-08 21:02 ` Tanstaafl
2010-03-08 22:41 ` Dale
2010-03-06 12:17 ` Peter Humphrey
2010-03-06 19:28 ` Tanstaafl
2010-03-07 10:21 ` Peter Humphrey
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=201003052120.01622.alan.mckinnon@gmail.com \
--to=alan.mckinnon@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