From: Antonio M D'souza <adsouza@student.math.uwaterloo.ca>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Re: gcc 3.0
Date: 03 May 2002 08:04:06 -0400 [thread overview]
Message-ID: <1020427446.28115.2.camel@quikbox.ca> (raw)
In-Reply-To: <Pine.LNX.4.44.0205022246420.11651-100000@callisto.scs.ryerson.ca>
Actually, you will need to completely switch emerge profiles to the new
gcc3 profile and then rebuild the world.
This is because C++ stuff built with gcc3 is not binary compatible with
the stuff compiled by gcc2.95
And, since there isn't a way to distinguish between C++ and C in the
portage system, you have to play it safe by rebuilding it all.
emerge -e world
should do the trick, methinks.
On Thu, 2002-05-02 at 22:50, Michael Reid - CSCI/P2001 wrote:
> > I have a machine at home I built from scratch using gcc3 and it works
> > beautifully, with the one drawback that I cannot seem to get kdelibs to
> > compile with gcc3 for the life of me. If anyone knows a workaround I'd
> > love to get kde3 going on that machine ... otherwise I'll stick with
> > gnome for now. The gcc3 compiled machine does seem snappier, but that
> > may be psychosomatic. :-)
> >
>
> How would I go about upgrading my gcc2.95 system to a fully gcc3.0 system?
>
> Is it as simple as:
>
> emerge gcc
> emerge --emptytree --update world
>
> ??
>
> What about the bootstrap process?
>
> Thanks.
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
--
613-233-6434
www.quikbox.ca
JabberID: quik@jabber.com
180 Lees Ave, #407, Ottawa, K1S 5J6
prev parent reply other threads:[~2002-05-03 12:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020502202702.A56B3AC506@chiba.3jane.net>
2002-05-03 2:50 ` [gentoo-dev] Re: gcc 3.0 Michael Reid - CSCI/P2001
2002-05-03 12:04 ` Antonio M D'souza [this message]
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=1020427446.28115.2.camel@quikbox.ca \
--to=adsouza@student.math.uwaterloo.ca \
--cc=gentoo-dev@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