[SM-Discuss] new glibc hits stable
Arwed von Merkatz
v.merkatz at gmx.net
Thu Feb 24 18:05:11 EST 2005
On Thu, Feb 24, 2005 at 01:46:08PM -0800, Eric Sandall wrote:
> Quoting Arwed von Merkatz <v.merkatz at gmx.net>:
> > Hi everyone,
> > as discussed previously I integrated the new glibc spell to stable
> > today.
> > In other news I'm now working on a gcc33 spell installing to /opt for
> > the stuff that won't compile with gcc 3.4 (the one I know about right
> > now is openoffice). As soon as that's done - if I didn't do a mistake it
> > should be done as soon as my test cast finishes - I'll get it into the
> > grimoire and integrate the gcc 3.4 spells into test.
> > A warning to everyone on test grimoire who can't afford to recompile a
> > lot of stuff right now: gcc 3.4 comes with yet another binary
> > incompatible libstdc++, so all c++ programs have to be recompiled after
> > it's updated. If you don't want to do all those recompiles now you
> > should put gcc on hold.
> And hold g++. ;)
Yeah, both gcc and g++ should be put on hold there.
This should be made clear for those who didn't follow what we did with
gcc quite some time ago in devel:
gcc isn't one spell anymore, it's a set of spells. Each one of those
spells installs one of the compilers the gcc can provide. There's 'gcc',
which provides the C compiler and the basic infrastructure needed for
everything, "g++" for the C++ compiler, "g77" for the Fortran compiler,
"gcj" for the java compiler and "ada" for the ada95 compiler.
Overall that means longer compile times to get the compilers themselves
installed, as all of them compile the C compiler first before doing
the additional language, but the added flexibility is worth that.
Arwed v. Merkatz Source Mage GNU/Linux developer
More information about the SM-Discuss