| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Chris Gianelloni wrote: |
| 5 |
> Use a generic stage. Do not use an i686 stage3 as a seed, use an x86 |
| 6 |
> one. Your stage1 subarch should be "x86" not "i686"... I would also |
| 7 |
> suggest not using the C(XX)FLAGS you've chosen. Add a -march=i686. |
| 8 |
> You're already building i686-only binaries via subarch i686, it makes no |
| 9 |
> sense to under-optimize the binaries, too. ;] |
| 10 |
|
| 11 |
I've managed to create a x86 stage1 using stage3-x86-2007.0 as a seed. |
| 12 |
Due to the fact that seed's CHOST is i486-pc-linux-gnu I had to choose |
| 13 |
the same one in my stage1.spec - otherwise catalyst fails because of the |
| 14 |
obvious lack of i686-pc-linux-gnu-gcc. As a result I've got a stage1 |
| 15 |
with subarch x86 and CHOST i486-pc-linux-gnu. Now I'm trying to create a |
| 16 |
stage2 with the target i686-pc-linux-gnu CHOST and i686 subarch. |
| 17 |
catalyst fails to emerge any package due to lack of |
| 18 |
i686-pc-linux-gnu-gcc. No such file in the used stage1 tarball indeed. |
| 19 |
|
| 20 |
What am I doing wrong? Should I change CHOST only between stage2 and 3? |
| 21 |
Or is there a different solution? I'd be grateful for your support. |
| 22 |
.spec files attached. |
| 23 |
|
| 24 |
Regards, |
| 25 |
Jan Stępień |
| 26 |
-----BEGIN PGP SIGNATURE----- |
| 27 |
Version: GnuPG v1.4.7-ecc0.1.6 (GNU/Linux) |
| 28 |
|
| 29 |
iD8DBQFHPh+aV8Af0wiAIQIRAnomAKCIBzzHg7kQm2MnCtsTKFXZbS+0+QCeOsR7 |
| 30 |
SjZwnrzMBDCfNhxnY76+k4E= |
| 31 |
=zhka |
| 32 |
-----END PGP SIGNATURE----- |
Archives