public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-dev] Bugs in autoconf/automake and python-fchksum
@ 2005-09-12 12:41 Frank Schafer
  2005-09-12 12:47 ` Henrik Brix Andersen
  0 siblings, 1 reply; 4+ messages in thread
From: Frank Schafer @ 2005-09-12 12:41 UTC (permalink / raw
  To: gentoo-dev

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



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [gentoo-dev] Bugs in autoconf/automake and python-fchksum
  2005-09-12 12:41 [gentoo-dev] Bugs in autoconf/automake and python-fchksum Frank Schafer
@ 2005-09-12 12:47 ` Henrik Brix Andersen
  2005-09-12 12:49   ` Frank Schafer
  0 siblings, 1 reply; 4+ messages in thread
From: Henrik Brix Andersen @ 2005-09-12 12:47 UTC (permalink / raw
  To: gentoo-dev

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [gentoo-dev] Bugs in autoconf/automake and python-fchksum
  2005-09-12 12:47 ` Henrik Brix Andersen
@ 2005-09-12 12:49   ` Frank Schafer
  2005-09-12 12:56     ` Mike Frysinger
  0 siblings, 1 reply; 4+ messages in thread
From: Frank Schafer @ 2005-09-12 12:49 UTC (permalink / raw
  To: gentoo-dev

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



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [gentoo-dev] Bugs in autoconf/automake and python-fchksum
  2005-09-12 12:49   ` Frank Schafer
@ 2005-09-12 12:56     ` Mike Frysinger
  0 siblings, 0 replies; 4+ messages in thread
From: Mike Frysinger @ 2005-09-12 12:56 UTC (permalink / raw
  To: gentoo-dev

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



^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2005-09-12 13:02 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-09-12 12:41 [gentoo-dev] Bugs in autoconf/automake and python-fchksum Frank Schafer
2005-09-12 12:47 ` Henrik Brix Andersen
2005-09-12 12:49   ` Frank Schafer
2005-09-12 12:56     ` Mike Frysinger

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox