installing 2004.3 bootstrap.sh glibc error

[Reinder]

Hi all

im installing gentoo on a AMD K6 and i get this error when bootstrap reaches glibc:

[Reinder]

I still can't install this PC

can anyone help me plz?
I want to make this server

first i had fedora core 2 on it.. it worked great..
but the rpm's made me crazy.

and i have gentoo on my other PC's so i tried gentoo this time

this PC needs to be my DHCP / DNS / Firewall
maybe some suggestion for another distro

[Suicidal]

[rjw8703]

Go to documents thread. Most of all of your questions about installation
will be answered there.

[Reinder]

ok tnx i will try that

[Dud3!]

I couldn't get past glibc yesterday either...

https://forums.gentoo.org/viewtopic.php?t=257531
_________________
"There's no problem so large it can't be solved by killing the user off, deleting their files, closing their account and reporting their REAL earnings to the IRS"

[Reinder]

i followed this documentation

https://forums.gentoo.org/viewtopic.php?t=189250

but it stops with the same error but this time at 20041102
i guess this is because in this guide ACCEPT_KEYWORD='~x86' is set

[monkey89]

As the error states, segmentation faults are generally caused by one of two things:

1) Aggressive CFLAGS (OS Problem).

I don't know what your cflags are, so post them here (and make sure you do it exactly; if you make a typo we can't tell if that's what is causing the error or if that error doesn't really exist). You should try sticking to something simpler to see if it alleviates the error.

2) Hardware Error.

Your computer may be suffering from a memory problem - I recommend running memtest from a LiveCD. Just take a Gentoo LiveCD and in the boot prompt, enter "memtest86". If it runs for a while error-free, I'm out of ideas. However, if you get an error, it's time to replace the memory.

[Reinder]

1)

[Reinder]

[justin.c]

i had trouble bootstrapping glibc too, with same error, kept happening in random places... until i turned back the clock on my cpu from the 2.66GHz i had overclocked too, back to 2GHz... is ur cpu overclocked? if so, turn it back... overclocked cpus seem to cause lots of problems

[Reinder]

no it's not overclocked

it's an AMD K6 running on 400 MHz

[Imago]

i think there were some troubles with the k6 cflag. Im not sure about it and i cant find the bug for now. But maybe you should try to set -mcpu to i586.

CU
Imago

[Reinder]

ok, i will try that
you will hear if this worked or not

[Reinder]

now it stops at gettext

[Imago]

hm although I more and more think its actually a hardware issue, you can of course try to remove all those cflags and then try it again.
But really doubt that this is the reason.

Did you run the 'memtest86' as monkey89 said?

CU
Imago

[Reinder]

look my post earlier

memtest86 won't run

and the PC is fine i think, because Fedora Core 2 runned on it too

[corsair]

Hi,

did you try to execute that memtest86 file? If yes, this is not the correct way to run memtest86. You have to enter memtest86 right after your cd boots, or that is to say when you select your kernel.

Markus

[Reinder]

ahh thanks

i have to type it a the bootloader?
i'll try that

[Reinder]

memtest86 runs without errors

[monkey89]

Doing it for a few minutes doesn't work: you're compiling for longer than that, so taxing the system for just a short period of time won't do anything.

Run it for at least a few hours and see if anything comes up. Sporadic compiler errors are generally hardware errors. Fedora Core 2 probably worked because the load required to do basic tasks or install it is a lot less than compiling software. I'll bet that if you tried compiling something big in FC2 or did some high-load task, it would fault as well.

-Monkey

[Reinder]

the memtest was at 100% and started over again..
so what's the point of running it again?

[LordBug]

Just because it passed once, doesn't mean it's fine.

I had a PC that I knew had to have flaky RAM, but didn't know which DIMM it was. I ran a memchecker program for over 5 hours before the problem DIMM finally surfaced. It had passed the complete test over 20 times before it failed.

I would suggest running memtest86 for no less than 12 hours. Let it go all night. Also, I would suggest looking into a possible overheating issue. It's amazing how much work compiling is on a CPU and how fast they heat up because of it.

[Reinder]

if overheating will be the reason why would it always would stop at the same spot ?

I will try to do a stage 2 or 3 install

[Reinder]

stage 2 quits at the first package in emerge system :S > patch
at the configure script

well i stop trying.. thanks anyway for helping me so far