[gentoo-dev] Bugs in autoconf/automake and python-fchksum

[gentoo-dev] Bugs in autoconf/automake and python-fchksum

[Frank Schafer]

Hi,

It took me the whole weekend to build a stage1 system. (Took 5 hours
during last night ;)

I had to work around the bugs this way:

scripts/bootscripts.sh
emerge --oneshot --nodeps autoconf
emerge --oneshot --nodeps autoconf-wrapper

This solved the problem, that automake installed during ``emerge
system'' has a autoconf dependency of a not installed autoconf set what
broke ``emerge system''.

emerge --oneshot --nodeps python

During ``emerge system'' python-fchksum failed with a not existing
i386-pc-linux-gnu-gcc on a i686 system. I don't know if python hard
codes the native compiler to the one it was built with or if this
compiler is hard coded in setup.py during python installation. Looking
at the ebuild it seems to be ok.

The native compiler should come from the CHOST setting in make.conf.

after the 3 ``emerge --oneshot''s after bootstrap ``emerge system''
succeeded.


Regards
Frank


-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Bugs in autoconf/automake and python-fchksum

[Henrik Brix Andersen]

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

On Mon, 2005-09-12 at 14:41 +0200, Frank Schafer wrote:
> During ``emerge system'' python-fchksum failed with a not existing
> i386-pc-linux-gnu-gcc on a i686 system. I don't know if python hard
> codes the native compiler to the one it was built with or if this
> compiler is hard coded in setup.py during python installation. Looking
> at the ebuild it seems to be ok.

https://bugs.gentoo.org/show_bug.cgi?id=88777

./Brix
-- 
Henrik Brix Andersen <brix@gentoo.org>
Gentoo Metadistribution | Mobile computing herd

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

Re: [gentoo-dev] Bugs in autoconf/automake and python-fchksum

[Frank Schafer]

On Mon, 2005-09-12 at 14:47 +0200, Henrik Brix Andersen wrote:
> On Mon, 2005-09-12 at 14:41 +0200, Frank Schafer wrote:
> > During ``emerge system'' python-fchksum failed with a not existing
> > i386-pc-linux-gnu-gcc on a i686 system. I don't know if python hard
> > codes the native compiler to the one it was built with or if this
> > compiler is hard coded in setup.py during python installation. Looking
> > at the ebuild it seems to be ok.
> 
> https://bugs.gentoo.org/show_bug.cgi?id=88777
> 
> ./Brix

Yes, there I got the workaround from. Be this there this isn't a reason
to fix the bug?

-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Bugs in autoconf/automake and python-fchksum

[Mike Frysinger]

On Monday 12 September 2005 08:49 am, Frank Schafer wrote:
> On Mon, 2005-09-12 at 14:47 +0200, Henrik Brix Andersen wrote:
> > On Mon, 2005-09-12 at 14:41 +0200, Frank Schafer wrote:
> > > During ``emerge system'' python-fchksum failed with a not existing
> > > i386-pc-linux-gnu-gcc on a i686 system. I don't know if python hard
> > > codes the native compiler to the one it was built with or if this
> > > compiler is hard coded in setup.py during python installation. Looking
> > > at the ebuild it seems to be ok.
> >
> > https://bugs.gentoo.org/show_bug.cgi?id=88777
>
> Yes, there I got the workaround from. Be this there this isn't a reason
> to fix the bug?

just because it's fixed in the portage tree doesnt mean it is fixed in the 
stages
-mike
-- 
gentoo-dev@gentoo.org mailing list