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 syst
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 th
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
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 ``em
