From: Philip Webb <purslow@ca.inter.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] libtool 2.x upgrade
Date: Thu, 25 Feb 2010 22:25:32 -0500 [thread overview]
Message-ID: <20100226032532.GE4353@ca.inter.net> (raw)
In-Reply-To: <4B87209D.8010704@gmail.com>
100226 bn wrote:
> I have a stable x86 system that requires still a bit of updating,
> among those libtool and gcc. Since I need the system to be usable *now*
> for work reasons, I don't feel like updating gcc and rebuilding it all
> with an emerge -e system / emerge -e world,
> but more and more packages want to upgrade to libtool 2.x
> Is it safe to upgrade libtool without (1)rebuilding gcc too
> and (2)rebuilding system/world?
FWIW I've been using Libtool 2.2.6b since 091212
& GCC 4.3.4 since 091018 without any problems I can remember;
I kept GCC 4.1.2 installed as well & use 'quickpkg' to make back-ups.
You shouldn't need to rebuild anything else till it comes up naturally.
I never do 'emerge world' without '-Dup', but emerge pkgs individually.
--
========================,,============================================
SUPPORT ___________//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O----------O---' purslowatchassdotutorontodotca
next prev parent reply other threads:[~2010-02-26 4:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 1:15 [gentoo-user] libtool 2.x upgrade bn
2010-02-26 2:41 ` [gentoo-user] " Nikos Chantziaras
2010-02-26 10:54 ` bn
2010-02-26 3:25 ` Philip Webb [this message]
2010-02-26 9:07 ` [gentoo-user] " Neil Bothwick
2010-02-26 13:33 ` bn
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=20100226032532.GE4353@ca.inter.net \
--to=purslow@ca.inter.net \
--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