-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris Gianelloni wrote: > 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. ;]
I've managed to create a x86 stage1 using stage3-x86-2007.0 as a seed. Due to the fact that seed's CHOST is i486-pc-linux-gnu I had to choose the same one in my stage1.spec - otherwise catalyst fails because of the obvious lack of i686-pc-linux-gnu-gcc. As a result I've got a stage1 with subarch x86 and CHOST i486-pc-linux-gnu. Now I'm trying to create a stage2 with the target i686-pc-linux-gnu CHOST and i686 subarch. catalyst fails to emerge any package due to lack of i686-pc-linux-gnu-gcc. No such file in the used stage1 tarball indeed. What am I doing wrong? Should I change CHOST only between stage2 and 3? Or is there a different solution? I'd be grateful for your support. .spec files attached. Regards, Jan Stępień -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7-ecc0.1.6 (GNU/Linux) iD8DBQFHPh+aV8Af0wiAIQIRAnomAKCIBzzHg7kQm2MnCtsTKFXZbS+0+QCeOsR7 SjZwnrzMBDCfNhxnY76+k4E= =zhka -----END PGP SIGNATURE-----
subarch:i686 version_stamp: 7.11 target: stage2 rel_type: default profile: default-linux/x86/2007.0 snapshot: snapshot source_subpath:default/stage1-x86-7.11 distcc_hosts: 192.168.1.101 pkgcache_path:/var/tmp/catalyst/packages chost: i686-pc-linux-gnu cflags: -Os -pipe -march=i686 -fomit-frame-pointer
subarch:x86 version_stamp: 7.11 target: stage1 rel_type: default profile: default-linux/x86/2007.0 snapshot: snapshot source_subpath:stage3-x86-2007.0 distcc_hosts: pkgcache_path:/var/tmp/catalyst/x86_packages_stage1 chost: i486-pc-linux-gnu cflags: -Os -pipe -mtune=i686 -fomit-frame-pointer
