| 1 |
Actually, you will need to completely switch emerge profiles to the new |
| 2 |
gcc3 profile and then rebuild the world. |
| 3 |
This is because C++ stuff built with gcc3 is not binary compatible with |
| 4 |
the stuff compiled by gcc2.95 |
| 5 |
And, since there isn't a way to distinguish between C++ and C in the |
| 6 |
portage system, you have to play it safe by rebuilding it all. |
| 7 |
emerge -e world |
| 8 |
should do the trick, methinks. |
| 9 |
|
| 10 |
On Thu, 2002-05-02 at 22:50, Michael Reid - CSCI/P2001 wrote: |
| 11 |
> > I have a machine at home I built from scratch using gcc3 and it works |
| 12 |
> > beautifully, with the one drawback that I cannot seem to get kdelibs to |
| 13 |
> > compile with gcc3 for the life of me. If anyone knows a workaround I'd |
| 14 |
> > love to get kde3 going on that machine ... otherwise I'll stick with |
| 15 |
> > gnome for now. The gcc3 compiled machine does seem snappier, but that |
| 16 |
> > may be psychosomatic. :-) |
| 17 |
> > |
| 18 |
> |
| 19 |
> How would I go about upgrading my gcc2.95 system to a fully gcc3.0 system? |
| 20 |
> |
| 21 |
> Is it as simple as: |
| 22 |
> |
| 23 |
> emerge gcc |
| 24 |
> emerge --emptytree --update world |
| 25 |
> |
| 26 |
> ?? |
| 27 |
> |
| 28 |
> What about the bootstrap process? |
| 29 |
> |
| 30 |
> Thanks. |
| 31 |
> |
| 32 |
> _______________________________________________ |
| 33 |
> gentoo-dev mailing list |
| 34 |
> gentoo-dev@g.o |
| 35 |
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev |
| 36 |
-- |
| 37 |
613-233-6434 |
| 38 |
www.quikbox.ca |
| 39 |
JabberID: quik@××××××.com |
| 40 |
180 Lees Ave, #407, Ottawa, K1S 5J6 |
Archives