| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Releng, |
| 5 |
After messing with http://bugs.gentoo.org/show_bug.cgi?id=51277, I have |
| 6 |
found an interesting quirk in the GRP build process. |
| 7 |
|
| 8 |
It looks like the GRP set this user had was seeded with a x86 stage3. |
| 9 |
How can I tell? His perl modules are being put into a i386 directory, |
| 10 |
which is the CHOST of x86 optimized release media. I duplicated the |
| 11 |
behavior by building two GRP sets, one with a x86 seed stage3, and one |
| 12 |
with a pentium3 seed stage3. You guessed right - seeding with the |
| 13 |
pentium3 stage solved the problem. |
| 14 |
|
| 15 |
So, the moral of the story is, seed your GRP builds with a stage3 that |
| 16 |
matches your subarch, or else things that depend on CHOST, like perl, |
| 17 |
will be broken (and Chris will chase you naked through the jungle with |
| 18 |
his QA axe). |
| 19 |
|
| 20 |
Cheers, |
| 21 |
- -- |
| 22 |
John Davis |
| 23 |
Gentoo Linux Developer |
| 24 |
<http://dev.gentoo.org/~zhen> |
| 25 |
|
| 26 |
- ---- |
| 27 |
GnuPG Public Key: <http://dev.gentoo.org/~zhen/zhen_pub.asc> |
| 28 |
Fingerprint: 4F9E 41F6 D072 5C1A 636C 2D46 B92C 4823 E281 41BB |
| 29 |
-----BEGIN PGP SIGNATURE----- |
| 30 |
Version: GnuPG v1.2.4 (GNU/Linux) |
| 31 |
|
| 32 |
iD8DBQFAzcrxuSxII+KBQbsRAqw+AKCGpyA3NMP/sew3VDaEN1C7ObV5EgCfU1SX |
| 33 |
zy98EfiYYTa3Q/AUZdlkAPQ= |
| 34 |
=Qoie |
| 35 |
-----END PGP SIGNATURE----- |
| 36 |
|
| 37 |
-- |
| 38 |
gentoo-releng@g.o mailing list |
Archives