Is gentoo-1.3-final going to base on gcc-3.2?

Ypsilon

You maybe have noticed that the gcc-develplan was changed and
the gcc-3.2 will come out on tuesday.

As it is supposed to be the new default compiler for future distros, I hope gentoo will switch to gcc-3.2 with the 1.3 (or maybe already 1.3c??) release.
So is that planned?

Ypsilon
_________________
gentoo ownz.

therobot · Apprentice Joined: 07 Jun 2002 Posts: 256 Location: Canada

there isn't going to be a 1.3(or so I'm led to believe). When it goes stable it's going to be 1.4. Not sure about the gcc, but it'll probably be 3.2.

neuron · Advocate Joined: 28 May 2002 Posts: 2371

Ypsilon · Posted: Sun Jul 21, 2002 7:11 pm Post subject: Well,...

...now I read this:

We're currently in the final testing stages towards launching a release enabling a full installation with gcc3.1 as the default compiler

But wouldn't it be better to switch to gcc-3.2 instead of 3.1 as no one will care about 3.1 anymore in a few weeks?
_________________
gentoo ownz.

trythil · Posted: Sun Jul 21, 2002 7:51 pm Post subject:

xorbe · Posted: Mon Jul 22, 2002 12:15 am Post subject:

trythil · Posted: Mon Jul 22, 2002 5:37 am Post subject:

proxy · Posted: Mon Jul 22, 2002 5:56 am Post subject:

i would rather have a 3.2 system as it is not a big deal (1 day) either way to start from scratch or recomile whole system to upgrade...

proxy

Erukian · Posted: Wed Jul 24, 2002 8:49 pm Post subject:

proxy, im with your 100%.

When gentoo 3.1.1 comes out, and if gentoo 1.3c or whatever goes with that then a *few days later* gentoo will be outdated because a bugfix came out. People using stage2 or stage3 cd's will be stuck with a bugged out compiler thats not compatible with gcc3.2 binary's.

It seems like a bad move to go onto gcc3.1.1 even though its tested, why not release with gcc3.2? Gcc3.2 is the product of the testing of gcc3.1.1 so it cant be all that horrible to stick it i a gentoo 1.3(c/final)

pjp · Administrator Joined: 16 Apr 2002 Posts: 20067

hubick · n00b Joined: 23 Jul 2002 Posts: 8

The only difference between 3.2 and 3.1.1 are a few ABI bugs. The GCC folks could have just named what will be 3.2 as 3.1.1, except for the fact that you don't want to break binary compatability in a minor point release. As I understand it reading the list, the main reason 3.1.1 is being released at all is because Apple wants it. Moving from 3.1 to 3.2 is not, in my mind, something that requires a HUGE amount of testing, if anything, as it should FIX things rather than break them. Don't think of it as a major release, because the only reason it is being label as that is because of binary compatibility - other than that, it basically IS 3.1.1.

I think Gentoo should easily be able to upgrade to 3.1, and I hope they do, as 3.2 should finally bring a somewhat stable ABI and the binary compatibility everyone wants.

Forge · Posted: Fri Jul 26, 2002 3:27 pm Post subject:

So we all make GCC 3.2 become 1.3c and move back the 1.4 release timetable. Simple problem, simple solution.

As soon as we have a GCC 3.2 ebuild, I'll just rebuild everything. emerge -e world ought to hit everything, right?

Scott Frappier · n00b Joined: 08 May 2002 Posts: 57

verwilst · n00b Joined: 16 Apr 2002 Posts: 30 Location: Belgium, Gent

Hehe, those assumptions you guys make is fun to read

)

Here's the real deal:

Gentoo 1.4 will have gcc 3.2.
I already have a stage1 tarball, but i won't upload it yet, since i'm going to redo it, after we fix a couple of issues before the real work starts.
I'm going to do my best to get Gentoo 1.4 ready for the Expo on the 13th (i think), so stay tuned

)

See ya!
_________________
Bart Verwilst
Gentoo Linux Developer
Gent, Belgium

Jyrinx · Posted: Wed Jul 31, 2002 2:02 am Post subject:

Is there gonna be a 1.3c release after all?

verwilst · n00b Joined: 16 Apr 2002 Posts: 30 Location: Belgium, Gent

Nope, since i'll be basing directly on GCC 3.2, i think it's more clear to up the version to 1.4 directly.
_________________
Bart Verwilst
Gentoo Linux Developer
Gent, Belgium

Jyrinx · Posted: Thu Aug 01, 2002 1:57 am Post subject:

Ah. Well, I was planning to take the plunge when 1.3c came out ... will there be any test ISOs based on 3.2 before 1.4 is unleashed (theoretically) in a few weeks? (Or, how would one go about a fresh install of Gentoo 1.3b with GCC 3.2?)

Jyrinx
jyrinx_list@mindspring.com

caveman · n00b Joined: 09 Jun 2002 Posts: 12 Location: UK

I've done a fresh install from a 1.2 disc using GCC3.2pre. Worked OK. You need to 'emerge rsync' then do the emerge gcc trick before bootstrapping (with -march=i486 -O3 -pipe) as has been described elsewhere. You also need to change the link to the default profile so that it points to the gcc3 profile and unmask gcc3.2pre before doing the emerge gcc. After this is done, change the processor optimisations to what you really want and bootstrap. After that everything went pretty normally. GCC3.2pre occassionally stops with 'Internal Compiler Error' but just restart the ebuild that it broke on. It does it less than GCC3.1 did though.
I've got KDE and pretty much everything else working fine now.

Just remember that any subsequent rsync currently remasks gcc3.2pre and an emerge -u world will then try to compile gcc3.1. You must remember to unmask gcc3.2pre everytime.

AlterEgo · Veteran Joined: 25 Apr 2002 Posts: 1619

Maybe this a a really dumb question:

I'm thinking about binary versions of java/Flash and other binary-only packages:
Once they have been made available for use with GCC 3.1, will they also work with 3.2?

zigg · n00b Joined: 18 Jun 2002 Posts: 8

caveman · n00b Joined: 09 Jun 2002 Posts: 12 Location: UK

Well I've had GCC2.95.3 crash a few times on a overclocked machine (a slotA Athlon 750 clocked to 1GHz on a flaky mainboard) but this particular machine is actually clocked to the correct rated speeds (It's a athlonXP 1700+) and NEVER crashes using GCC2.95.3 and has only done it once using GCC3.2pre. It did it more often with GCC3.1 so I figured it was just buggy :wink:

Bear in mind GCC3.2pre is a prerelease snapshot. It's not GCC3.2 final.