Yeah, thanks everyone for your input. I ran memtest86, and it appears
that the last 30 megs of my ram fail one of the tests. Problem
solved. I switched it with another stick I had lying around, and
everything compiles just fine. Now to try and get a new stick under
As soon as you mentioned the idea that the ram might be bad, it seemed
completely obvious that was the problem, even though I'd been puzzling
over it for days. Thanks a lot people.
On Fri, 26 Nov 2004 09:32:09 -0700, Duncan <1i5t5.duncan@...> wrote:
> Boyusmaximus posted <fec0e46d04112602396b094cb1@...>, excerpted
> below, on Fri, 26 Nov 2004 10:39:10 +0000:
> > Hi, I'm having terrible problems reinstalling gentoo. Using the new
> > 2004.3 minimal live cd, I progress to the point where I need to
> > bootstrap my system, and I hit trouble. Everytime I try to run the
> > bootstrap script, it fails at a random point along the way. I seem to
> > always hit a segmentation fault or 'unnamed error' (my favourite kind)
> > but at different points along the way, sometimes as early as building
> > glibc, other times as late as building gcc. I guess this is some kind
> > of hardware fault,
> Yes. Random points along the way almost certainly means hardware.
> What I did here is analyze the bootstrap script and execute the individual
> steps one by one that it would have run. That was with 2004.0 (which I
> never did get to work, because by the time I figured things out to the
> point I wanted, 2004.1 was close enough that I decided to wait) and 2004.1
> (which /did/ work for me). Back then, and I imagine it's still the same,
> the majority of the bootstrap script was simply checking what versions
> were in the portage tree for it to build and that each one fit the
> requirements of the profile. The actual bootstrap build process ended up
> being about three lines of code (build one set with both use=bootstrap and
> use=build set, unset one to build the next set, then do an environment
> update necessary before building the third set) altho spread out in about
> 15 lines of "glue" code near the end of the bootstrap script.
> Thus, what you do is
> 1) set all the environmental variables it would set, by hand (or manually
> set an exit at an appropriate point in the bootstrap script, then "source"
> it so it executes in the same command shell you are using, setting the
> environment accordingly), ensuring build and bootstrap are in your USE
> variable as well, then
> 2) emerge each package in turn of the first set
> 3) unset build or bootstrap (don't recall which, but its in the bootstrap
> script so it's easy to see)
> 4) emerge each package in turn in the second set
> 5) update your environment using env-update, where the script would do so
> 6) continue, emerging each package in turn of the third set from the
> 7) tie up any config loose ends and unset the other one of
> build/bootstrap, as the bootstrap script does to finish off.
> You are then left where you'd be if you'd just finished bootstrap, and can
> resume the gentoo installation process from the handbook.
> Again, note that the above steps may have changed slightly since I did it
> with 2004.1 -- the bootstrap script had changed a bit between that and
> 2004.0, and that was before portage 2.0.51 and cascading profiles, so it's
> likely changed a bit further now. However, it's certainly possible to
> follow the bootstrap script for anyone that has a bit of bash scripting
> under their belt, and the above demonstrates roughly what's involved,
> besides actually parsing thru the script to understand what it's doing in
> the first place.
> I'm actually very glad I ended up doing it that way myself, because I
> ended up with a FAR better knowledge of the bootstrap process and the
> infrastructure that makes Gentoo (and by extension, virtually all Linux
> distributions) run, than I would have had if everything had "just worked"
> as it was outlined in the manual. As well, I did this in my spare time
> over several months (as I said, with several weeks off while waiting for
> 2004.1), a single ebuild package at a time, all the while running from
> Mandrake partitions on the same machine (which were eventually deleted
> when I got Gentoo up and running to my satisfaction). Over all that extra
> time, I was active in the various Gentoo groups (aka mailing lists, but I
> participate thru GMane's list2news gateway so they are newsgroups to me),
> including amd64 (naturally), user, and following announce and devel.
> Therefore, by the time I got far enough to encounter most of the problems
> other Gentoo newbies have (etc-updating away a site-specific fstab,
> anyone?), I had seen them long before covered on one group or another, and
> either avoided the issue or knew just what to do without myself having to
> ask. In fact, as I was already a Mandrake power user, having been active
> on their Cooker group/list for some time, and having migrated to amd64 on
> Mandrake, I had the rather unusual experience of being able to answer a
> number of questions in the user group in some detail, as well as
> participate in the discussion here and a couple times in the devel group
> too, well before I was even up and going on the Gentoo Linux platform!
> Thus, doing the bootstrap process manually instead of by script is not
> only possible, but something I'd recommend any serious user intent on
> learning about his system does at least once. It certainly benefited me!
> The caveat, of course, is that in ordered to do that, one must first have
> a decent understanding of bash scripting. In my case, that wasn't an
> issue, since I'd gained a working understanding of that early on in my
> Mandrake experience, by dissecting their boot scripts, actually splitting
> up sysinit.rc into multiple purpose based scripts as made sense to me,
> then eventually doing an update to a later version of their script, and
> similarly dissecting it, before giving up when I moved to Cooker and was
> regularly updating, just as ~amd64 does on Gentoo. However, that
> experience means I have at least a basic understanding of bash scripting,
> enough to debug anyway, tho not necessarily enough to write my own scripts
> of that complexity, and that was quite enough to take apart and
> manually follow the Gentoo bootstrap script as well, which is exactly what
> I did.
> Not everybody takes three months setting up their Gentoo system, but then
> again, not everybody knows as much about it before they've even finished
> stage three, as I did.
> Duncan - List replies preferred. No HTML msgs.
> "They that can give up essential liberty to obtain a little
> temporary safety, deserve neither liberty nor safety." --
> Benjamin Franklin
> email@example.com mailing list
firstname.lastname@example.org mailing list