Public SourceMage Discussion List

[flux <flux AT sourcemage.org>]

"Andraž 'ruskie' Levstik" (ruskie AT codemages.net) wrote [08.05.27 15:01]:
> That's easy... g++ needs gcc compiled first :) so it's gcc time+g++ time :)
> for a split g++ spell... Here's how it goes iirc.
> 
> gcc
> gcc+g++
> gcc+g+++gcj
> gcc+objc
> 
> So in all cases it adds the time for one gcc compile to the build and in
> some (i.e. gcj) more...

Is all that really necessary? If the different front-ends rely on the
same version of gcc that is currently installed, will sorcery really
rebuild the entire gcc just to install, say, objc? In case the way I've
explained this isn't clear, an example:

1) cast gcc (a necessary component) but do not cast any other front-ends
as yet (try for a minimal system to start out with)

2) later, it's decided that some applications/libraries which depend on
g++ are needed, so g++ is to be cast. No system updates have been done
(or the gcc toolset in the latest grimoire is the same as the version
currently installed). This is done by issuing cast g++.

At step (2), gcc is already installed from step (1). If the latest
gcc-like spells are all the same version as the gcc already installed,
does sorcery still re-cast gcc in order to resolve the cast of g++, or
does it just cast g++? I have a feeling that it will just cast g++, as
this is what my memory is telling me from how things progressed on my
own system (though that was rather long ago, so my memory may not be
correct). If so, then I don't see the big deal, as the time would be the
same whether they are separate spells or one big spell with CONFIGURE
options.

-- 
Justin "flux" Boffemmyer
Cauldron wizard and general mage
Source Mage GNU/Linux
http://www.sourcemage.org

Attachment: pgpq7lt3Bvj4M.pgp
Description: PGP signature