Hmm, I agree, and good point. Well, it might be a bit later than I thought before I get to the very end (that is, the end of the DIY stuff; not 'the end' where I have a new complete Slackware) but still going well.
Only place I have had an error lately was building VIM; there was one test failure (test 23) but I won't put too much stock into that till I rebuild all this with the libstdc++ fixed; I'm pretty sure that can be done, because one of the first times I built the first half of all this, libstdc++ passed all tests OK, so chances are the compiler flags will affect it. Everything else is very good though, and there is an obvious difference in speed compiling stuff now, over my host tools -- inside chroot, stuff seems to 'fly' :).

You don't need to worry about or even build g++ during the first or inetrmediate toolchain phases, since all the code for the tools is written in C. The g++ compiler is written in C and can be finally produced when you have the other early stuff working okay.
libstdc++ are the runtime libraries needed for running C++ programs. Notice that they get installed to the same directory where the compiler libs are? That's because C++ programs are dependent on the specific libraries of the compiler used to compile with. If you build a multi-compiler system, each compiler will have its' own libstdc++ libs even though each compiler is using the same glibc.

Hmm, thanks for that explanation Gnashley :)

All was going very well last night, but it seems there has been a wrench thrown into the gears, so to speak; I think my CPU bought the farm :/
It froze up while I was un-tarring something, and was totally hung. I rebooted but the 4 D-bracket lights are just ALL red, and nothing happens, no screen power-up, no beeps, no bios screen... I mean, the peripherals turn on, so there's power, and I still had video when it froze, so I presume the video card is OK, but I fear my CPU is toast :(

LOL, anyone got a spare socket 478 P4 lying around? :p
Well, in any event, the only other machine here that's internet-enabled is this hellish rotten Windoze heXP thing, so till I either get the modem in the laptop working (Zenwalk now) or find a new CPU, my project is obviously on hold, and I'll be updating a bit less here 'cause I REALLY dislike using this WXP machine I am typing on right now. I'm unemployed too, so it might be a while :/

Take care everyone!
~ As the Terminator said, "I'll be back."

Hmmm ....

When I was installing Gentoo (and compiling all those packages over a couple days), my laptop ran real hot ... I had to stop it for fear of meltdown. Technically it shouldn't meltdown, but who knows. I don't trust intel enough to gamble on whether excessive CPU usage for extended periods of time when my laptop is not optimally ventilated ... may cause meltdown.

Does the processor look toasted ?

(I would still bet that the processor is not toasted ... it may be something else in there that is toasted, beep codes would help)

Nah, there are no beep codes.. When I turn it on, it powers up, the drives all come on, the fans turn on, and the D-bracket stays all red. No beeps or anything, and my monitor doesn't power up either.
The monitor works, I had the laptop plugged into it today.
I suppose there is a remote chance my video card bit the dust, but if that were the case, I would get 8 beeps from the machine (from experience) but that doesn't happen.
I haven't yet opened up the machine, but I wouldn't expect to see physical signs of a burnt CPU, do you think?
I am 99% certain it wasn't a heat issue as I had the sensors monitored all the time, and lots of cooling.
I'll open it and have a peek tomorrow, but it sure looks like the CPU quit.

Ram Chip
 

Nother possibility would be a ram chip. if you have two could remove one try to boot, if not swap the chips and try booting again. Have lost 1 or 2 ram chips before compiling so it would not be unheard of. Would be as suspect to them as the processor though.

It could be a RAM stick too. But, usually, it still boots even if one is bad. Really, it could be many things. Just take a look inside and see if there's anything obviously wrong in there.

EDIT: for burn processor, here's what it looks like (AMDs tend to burn more often than pentiums ... pentiums automatically throttle down when they overheat. Newer AMDs have a kill switch that kills the processor on overheat .... theoretically, just in time to save the m-board from being melted through)

http://i2.neoseeker.com/a/OCguide/burnt1.jpg

That's a real shame! To have put all that effort into your project & then have your computer shuffle off it's mortal coil. Hope it turns out to be nothing too serious or expensive.

Brian

Ugh.. That does suck. Sorry to hear that GrapefruiTgirl... But yea, open it up and start poking around. Something may jump out at you.

Hiya people :)

Well, I poked around in there, to no avail.. Nothing appears out of place, nothing smells burnt; the processor socket looks like new, and the processor itself appears normal.
When I turn the machine on, with the CPU heatsink removed, I can feel the processor warm up quite quickly, though I can't compare how it feels to anything else, because it's the only one Ive ever tried this with.

I pulled out the memory, and turned the machine on; same deal. No go. There's only one memory stick in there.
Same with the video card removed; no beeps, no difference..

Just those same malicious red lights on the back of the box :/

Further suggestions welcome, but I am really suspecting the CPU -- anyone disagree?
I mean, I doubt it would be the northbridge, or some other obscure thing on the board, right? It's usually the PS, the CPU, the memory, or... well, that's about it, no?

the mainboard?
http://graphics.cs.uni-sb.de/new/upl...ics/elko02.jpg

really, could be just about anything. only way to know is to test every component in another box.

EDIT: about those lights: i guess it's better to ask around on hardware sites

Does the power supply seem ok ? Maybe it's failing.

If the processor doesn't look burnt, then it probably isn't. As erklaerbaer says, it's likely you'll have to test each component either in a another box or with testing equipment. (it's probably cheaper to do it in another box if you have one)

You could also take it to a repair shop ...

Remove Everything
 

Might try removing and disconnecting everything (except the pc speaker,lights, and power button connectors ) including the processor from the mb, clearing the cmos and then powerup the mb empty and see if you can get the error beeps from the mb.

Would narrow down do motherboard and power supply (or pc speaker ;) ).

Yikes, Erklaerbaer those are some nasty looking capacitors :) but mine don't look like that :p.

I will try powering the board with no cards and no processor, and see what happens..
As for the red lights, I did look up their meanings, and when all 4 are red, at apparently means the processor is either not installed or not working. When all is well, they change colors a bunch of times and when it's all booted up, they are all green.
I spose yes, it could be anything.. It could be the power supply. I can't afford to take it to a shop, so if I can't figure it out at home, then it'll hafta sit and wait.. I'll try Hern's suggestion..

Hmmm ... that's not good. So, all four light are red ? If so, that means it may just be the processor :(