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

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

[Jan Stępień]

[-- Attachment #1: Type: text/plain, Size: 1838 bytes --]

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

Hi everyone,

I already asked this question on Gentoo Forums, however my post remains
unanswered and I've thought that this is a better place for
catalyst-related inquires.

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:

# catalyst -s snapshot &&\
  catalyst -v -f stage1.spec &&\
  catalyst -v -f stage2.spec &&\
  catalyst -v -f stage3.spec &&\
  catalyst -v -f livecd-stage1.spec &&\
  catalyst -v -f livecd-stage2.spec

stage1 and stage2 have been created without any visible errors.
Generation of stage3 is being interrupted at emerging
dev-util/pkgconfig-0.21-r1

<snip>
checking for i686-pc-linux-gnu-g++... i686-pc-linux-gnu-g++
checking whether we are using the GNU C++ compiler... no
checking whether i686-pc-linux-gnu-g++ accepts -g... no
checking dependency style of i686-pc-linux-gnu-g++... none
checking how to run the C++ preprocessor... /lib/cpp
configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.

Grepping file lists of created stage1 and stage2 tarballs for "g++"
gives no results. There's no C++ compiler indeed.

The issue that might be important is the fact that I'm trying to compile
i686 stages on an amd64 machine, but on the other hand catalyst seems to
be conscious of this fact and doesn't protest. I'm using
catalyst-2.0.5_pre5.

Specfiles attached. Could you please help me and tell what mistake I've
made?

Regards,
Jan Stępień

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7-ecc0.1.6 (GNU/Linux)

iD8DBQFHPUwAV8Af0wiAIQIRAizyAJ4pp1+C7/TlnNUjVcJi6t+IatAq3QCgo54X
NOxSt8ZsXrh7fIRY0PFBW7g=
=Qqz1
-----END PGP SIGNATURE-----

[-- Attachment #2: stage1.spec --]
[-- Type: text/x-rpm-spec, Size: 317 bytes --]

subarch:i686
version_stamp: 7.11
target: stage1
rel_type: default
profile: default-linux/x86/2007.0
snapshot: snapshot
source_subpath:stage3-i686-2007.0
distcc_hosts:
portage_confdir:
portage_overlay:
pkgcache_path:/var/tmp/catalyst/packages
chost: i686-pc-linux-gnu
cflags: -Os -pipe -mtune=i686
cxxflags:
ldflags:


[-- Attachment #3: stage2.spec --]
[-- Type: text/x-rpm-spec, Size: 323 bytes --]

subarch:i686
version_stamp: 7.11
target: stage2
rel_type: default
profile: default-linux/x86/2007.0
snapshot: snapshot
source_subpath:default/stage1-i686-7.11
distcc_hosts:
portage_confdir:
portage_overlay:
pkgcache_path:/var/tmp/catalyst/packages
chost: i686-pc-linux-gnu
cflags: -Os -pipe -mtune=i686
cxxflags:
ldflags:


[-- Attachment #4: stage3.spec --]
[-- Type: text/x-rpm-spec, Size: 298 bytes --]

subarch:i686
version_stamp: 7.11
target: stage3
rel_type: default
profile: default-linux/x86/2007.0
snapshot: snapshot
source_subpath:default/stage2-i686-7.11
distcc_hosts:
portage_confdir:
portage_overlay:
pkgcache_path:/var/tmp/catalyst/packages
cflags: -Os -pipe -mtune=i686
cxxflags:
ldflags:

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

[Chris Gianelloni]

[-- Attachment #1: Type: text/plain, Size: 774 bytes --]

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.

-- 
Chris Gianelloni
Release Engineering Strategic Lead
Alpha/AMD64/x86 Architecture Teams
Games Developer/Foundation Trustee
Gentoo Foundation

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

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@gentoo.org mailing list

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

[Stephen Fromm]

On Fri, 2007-11-16 at 19:34 +0100, Jan Stępień wrote:
> -----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.

I ran into a similar problem as you did.  The problem is that the value
for pkgcache_path is the same for stages 1, 2, and 3 in your spec files.
As a result, the sys-devel/gcc package built in stage1 was reused in
stages 2 and 3.

I resolved this by specifying unique pkgcache_path values for all
catalyst targets (eg /var/tmp/catalyst/packages/<target>/<rel_type>).

Regards,
sf

-- 
gentoo-catalyst@gentoo.org mailing list

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

[Andrew Gaffney]

Stephen Fromm wrote:
> I resolved this by specifying unique pkgcache_path values for all
> catalyst targets (eg /var/tmp/catalyst/packages/<target>/<rel_type>).

Or just don't specify pkgcache_path at all and catalyst will provide a sane default.

-- 
Andrew Gaffney                                 http://dev.gentoo.org/~agaffney/
Gentoo Linux Developer             Catalyst/Installer + x86 release coordinator
-- 
gentoo-catalyst@gentoo.org mailing list

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

[Jan Stępień]

[-- Attachment #1: Type: text/plain, Size: 1372 bytes --]

-----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-----

[-- Attachment #2: stage2.spec --]
[-- Type: text/x-rpm-spec, Size: 303 bytes --]

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

[-- Attachment #3: x86_stage1.spec --]
[-- Type: text/x-rpm-spec, Size: 294 bytes --]

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

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

[Chris Gianelloni]

[-- Attachment #1: Type: text/plain, Size: 671 bytes --]

On Fri, 2007-11-16 at 23:54 +0100, Jan Stępień wrote:
> 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.

You should change the CHOST in the stage2 spec.  Look at
http://sources.gentoo.org/viewcvs.py/gentoo/src/releng/specs/2007.1/x86/
for examples.  Also, there's no need to post your specs every time.  It
just adds a bunch of stuff for people to download that don't necessarily
need it.

-- 
Chris Gianelloni
Release Engineering Strategic Lead
Alpha/AMD64/x86 Architecture Teams
Games Developer/Foundation Trustee
Gentoo Foundation

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]