Re: [gentoo-catalyst] Building stage3 fails because of no C++ compiler

[Jan Stępień]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chris Gianelloni wrote:
> On Fri, 2007-11-16 at 08:51 +0100, Jan Stępień wrote:
>> I've been trying to create a live CD using catalyst building my own
>> stage(1-3). I've downloaded stage3-i686-2007.0.tar.bz2 (MD5 sum
>> 55f18797e55a19f1f7d43d649f416504) and ran:
>
> Use a generic stage.  Do not use an i686 stage3 as a seed, use an x86
> one.  Your stage1 subarch should be "x86" not "i686"...  I would also
> suggest not using the C(XX)FLAGS you've chosen.  Add a -march=i686.
> You're already building i686-only binaries via subarch i686, it makes no
> sense to under-optimize the binaries, too.  ;]
>
> Let us know if those things didn't fix it.

Thanks a lot for your response. Meanwhile, I've managed to build all
three stages starting with the mentioned stage3-i686-2007.0. The method
I've came up with is following:

# catalyst -f stage1.spec
# rm -r <package dir>
# catalyst -f stage2.spec && catalyst -f stage3.spec

Actually I'm not sure whether removal of gcc package only wouldn't solve
the problem, but I have to admit I hadn't got neither time nor patience
to give it a try.

Nevertheless, thank you for your suggestion regarding optimisation. I
didn't know that the subarch variable in the *.spec file already makes
the output stage architecture exclusive. If so, I'll use march argument.

As long as information about results of building stages according to
your advice will be of any value for you, I'll let catalyst work
overnight. I hope I'll have some results in the morning (CET).

Best regards,
Jan Stępień
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7-ecc0.1.6 (GNU/Linux)

iD8DBQFHPeKZV8Af0wiAIQIRAnFXAKC5g5xsXF3NSJDZG5lLLs69/gf4QwCeI8pS
VtqFMeN+wNC+4wXa4+QEpsM=
=A5AA
-----END PGP SIGNATURE-----
-- 
gentoo-catalyst@g.o mailing list