bootsprap fails building glibc-2.2.5-r7

Robert K.

Hi,

I want to setup an new Gentoo 1.4RC1 System (Stage 1). The "Host" is an running Gentoo-Linux-System.

Bootstrap fails with following error-messages. Before I tried to bootstrap again, I executed always an emerge rsync.

Would be fine, If someone can help me.

rac · Posted: Tue Oct 29, 2002 1:32 pm Post subject:

Your CFLAGS and USE flags will probably be of interest.
_________________
For every higher wall, there is a taller ladder

Robert K. · Posted: Tue Oct 29, 2002 7:23 pm Post subject:

Hi,

I used following flags.

snipped from /etc/make.conf

USE="-gnome acl alsa crypt dga directfb dvd jpeg ldap mozilla mozirc perl samba slp tiff tcltk"
CHOST="i686-pc-linux-gnu"
CFLAGS="-march=athlon -O3 -pipe"
CXXFLAGS="${CFLAGS}"

Something I did'nt understand. The bootstrap-script replaces during the bootstrap-process my make.conf. So how can my Use-Flags prevent glibc from being compiled ?

Just as a try I commented my USE-Flags out. Glibc-Compile fails again ...

Bye
Robert

bertkenward · n00b Joined: 02 Aug 2002 Posts: 1 Location: Cambridge, UK

I've experienced a similar failure, using an rsync from yesterday ~19:00 GMT. Error message was:

Robert K. · Posted: Wed Oct 30, 2002 4:42 pm Post subject:

Hi,

I tried yet an stage3 install followed by an emerge rsync and emerge -e system . The same problems, glibc-compile fails.

Since Sunday I began every day an complete new installation with downloading/updating my portage-tree. No Chance.

One Time I had exactly the same error-messages as bertkenward.

Has somebody an explanation ?

Bye
Robert

thgreatoz · n00b Joined: 31 Oct 2002 Posts: 29

I've got the same problems, too...only when I extract the stage 1 tarball, I also get an odd error at the end, it says something like "Error, exit from before" or something along those lines, it makes no sense to me....

rac · Posted: Fri Nov 01, 2002 1:14 am Post subject:

dufeu · l33t Joined: 30 Aug 2002 Posts: 924 Location: US-FL-EST

Robert K. · Posted: Sun Nov 03, 2002 10:34 pm Post subject:

BoBB · Posted: Wed Nov 13, 2002 1:57 am Post subject:

Has anyone found a solution to this? Unfortunately booting to the 1.4RC1 CD is not an option for me and i would like to get this installed.

GroundControl · n00b Joined: 30 Jul 2002 Posts: 2 Location: New Zealand

I'm also having the same problem on an AMD K6-2 450.
CFLAGS="-march=k6-2 -O3 -pipe"
CXXFLAGS="${CFLAGS}"
I haven't changed any of the USE flags, so USE isn't defined as anything in make.conf.

The actual error line appears to be:

sharpie · n00b Joined: 14 Nov 2002 Posts: 4

I to have an AMD K6-2, 512 MB Ram, 1 Gig swap, and 2 Harddrives 8 + 15 Gig.

I am seeing a smiliar probelm with the Glibc compile..

And I'm also using:

CFLAGS="-march=k6-2 -O3 -pipe"
CXXFLAGS="${CFLAGS}"

texx · n00b Joined: 14 Nov 2002 Posts: 67 Location: Vienna

Hi.

I have the same problem posted above.

I have tried to install the 1.2 and the 1.4rc1 versions both fails.

Can it be a problem with my processor?? AMD k6 233 ???
I have read a article that the k6 has a bug, wich result in an error when copmile some program, like the kernel.

filoseta · n00b Joined: 09 Jun 2002 Posts: 9

Just a little background first:
My build system is a dual Athlon MP running off a 1.1a build from sometime this summer (constantly updated except gcc, so more like 1.2).

I have another HD installed and have been trying to load 1.4 (a few attemps over the past month and a half, it was not high priority) from withing my 1.1 build. This install method I have used well over 15 times on different systems, so I know it is not to fault.

The error messages that I have been getting over these past 6 weeks have matched Berkenward's problem to the letter. I had tried different stages, USE flags, gcc options and even gentoo 1.2, the builds stopped in the same place every single time.

Today I decieded to force using the new glibc (glibc-2.3.1-r2 currently masked), and hope for the best. To do this I changed the default-x86-1.4 profile and pointed it to the new glibc and binutils (I used the 2.13.90.10 rather than the .14 for no good reason) as well as unmasking those two ebuilds. NOTE: there are probably better ways to do this, but I was after a proof of compile.

It seems that my gamble has paid off so far. The bootstrap went without incodent and emerge system is about 2/3 of the way through. Of course I don't know of the system's stability at this point, but I figured that someone might be interusted in a possible resolution.

As a side note, after all of the different iterations I have attempted, it seems that glibc-2.2.5-r7 does not compile under a good portion of AMD processors. This is a rather broad generaliztion, but after attempting compiles on quite a few systems (amd and intel) under varying compile configurations, that is my current belief.

EDIT: not, a failure to compile in general, just on any systems based on the recent tarballs, as my 1.1 system has 2.2.5-r7 compiled and installed.

BoBB · Posted: Mon Nov 25, 2002 12:49 am Post subject:

What exactly did you change in which files to have it merge the new glibc on bootstrap? From looking at the files in /usr/portage/profile/default-x86-1.4/ I need to change something in either packages or packages.build but i wanted to make sure before i did something stoopid

filoseta · n00b Joined: 09 Jun 2002 Posts: 9

First off, as a disclaimer, this is most definately not the best way to do this. I have not yet invested the time learning the portage system to know the "right" way to make these changes. If anyone has, and knows a better way to do this, please post it.

What I did:
1)
/usr/portage/profiles/default-x86-1.4/packages
modify the two lines to match below (i.e. bump the versions)
*>=sys-devel/binutils-2.13.90.0.10
*>=sys-libs/glibc-2.3.1

2)
/usr/portage/sys-libs/glibc/glibc-2.3.1-r2.ebuild
remove the ~ in front of the x86

3)
/usr/portage/sys-devel/binutils/binutils-2.13.90.0.10
remove the ~ in front of the x86

4) /* critical */
cross fingers

5)
scripts/bootstrap.sh

I do not yet know what consiquences these changes will have upon an rsync. After the system is built I will rsync and make sure the ~'s were not added again. If they were I will probably move a copy of the ebuild's (without the ~'s) into my portage overlay directory and run some -p emerges to make sure portage doesn't try to merge the old versions of glibc and binutils.

Good luck and let me know if it works for you.

ekoontz · Posted: Thu Nov 28, 2002 10:19 am Post subject: workaround for this bug

I seem to have stumbled upon a workaround for this bug :
Put :

Lasker · Guru Joined: 17 Jul 2002 Posts: 445