[ILUG] GCC 3.0.2

[Colm MacCarthaigh]

On Mon, Jan 07, 2002 at 08:07:22PM +1100, Justin Mason wrote:
> 
> Stephane Dudzinski said:
> 
> > Well, considering that 2.95.3 is quite old now, i'm considering moving a
> > system to 3.0.2 for which packages exit.
> > Question: have you heard about bad things on 3.0.2 ?
> 
> yep -- ran into them firsthand. 
>

I've been using gcc 3.02 for a while now, as a 64-bit and 32-bit compiler
on solaris-sparc and as a 32 bit compiler on intel (linux debian), no probs
compling lots of stuff, C,C++,java and objective C. Use it to compile my
kernels and I've built koffice with it.

Didnt use packages though, built gcc from source :o)
 
> 	- C++ symbol mangling (and presumably other bin API stuff then)
> 	  changes between 2.96.xx and 3.0.2

still it seems to be consistent, and hasnt stopped anythign compiling,
unless yoy've got old objects hanging around ???

> 	- Red Hat KDE rpms are built with g++ 2.96-98.

well that's a Red Hat issue ;) red hat lose all sense when it comes to
gcc ;p

> result:
> 
> 	- you can't build any new KDE code with g++ from then on.

I've done this!!!

> 	- a world of pain

had some pain on sparc, but mainly due to non 64-bit clean socket functions
generating SIGBUS, that's a really a library/code problem.

> Not recommended!   There's supposedly compat RPMs as well, but they didn't
> help.

I'd recommend it, but from source :o)

-- 
-------------------------------------------------------------
colmmacc at redbrick.dcu.ie

"if you really want to change something, start with yourself"