| 1 |
On Fri, 2007-11-16 at 19:34 +0100, Jan Stępień wrote: |
| 2 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 3 |
> Hash: SHA1 |
| 4 |
> |
| 5 |
> Chris Gianelloni wrote: |
| 6 |
> > On Fri, 2007-11-16 at 08:51 +0100, Jan Stępień wrote: |
| 7 |
> >> I've been trying to create a live CD using catalyst building my own |
| 8 |
> >> stage(1-3). I've downloaded stage3-i686-2007.0.tar.bz2 (MD5 sum |
| 9 |
> >> 55f18797e55a19f1f7d43d649f416504) and ran: |
| 10 |
> > |
| 11 |
> > Use a generic stage. Do not use an i686 stage3 as a seed, use an x86 |
| 12 |
> > one. Your stage1 subarch should be "x86" not "i686"... I would also |
| 13 |
> > suggest not using the C(XX)FLAGS you've chosen. Add a -march=i686. |
| 14 |
> > You're already building i686-only binaries via subarch i686, it makes no |
| 15 |
> > sense to under-optimize the binaries, too. ;] |
| 16 |
> > |
| 17 |
> > Let us know if those things didn't fix it. |
| 18 |
> |
| 19 |
> Thanks a lot for your response. Meanwhile, I've managed to build all |
| 20 |
> three stages starting with the mentioned stage3-i686-2007.0. The method |
| 21 |
> I've came up with is following: |
| 22 |
> |
| 23 |
> # catalyst -f stage1.spec |
| 24 |
> # rm -r <package dir> |
| 25 |
> # catalyst -f stage2.spec && catalyst -f stage3.spec |
| 26 |
> |
| 27 |
> Actually I'm not sure whether removal of gcc package only wouldn't solve |
| 28 |
> the problem, but I have to admit I hadn't got neither time nor patience |
| 29 |
> to give it a try. |
| 30 |
|
| 31 |
I ran into a similar problem as you did. The problem is that the value |
| 32 |
for pkgcache_path is the same for stages 1, 2, and 3 in your spec files. |
| 33 |
As a result, the sys-devel/gcc package built in stage1 was reused in |
| 34 |
stages 2 and 3. |
| 35 |
|
| 36 |
I resolved this by specifying unique pkgcache_path values for all |
| 37 |
catalyst targets (eg /var/tmp/catalyst/packages/<target>/<rel_type>). |
| 38 |
|
| 39 |
Regards, |
| 40 |
sf |
| 41 |
|
| 42 |
-- |
| 43 |
gentoo-catalyst@g.o mailing list |
Archives