Related to Aaron's post, have you done an "emerge -Up world" to see if any of the libraries or gcc need to be updated? I know there has been a few updates to Portage in the past month or two, as well as an update to GCC recently. If it helps, I'm running version gcc-3.2.3-r2. You might be running into a situation where binutils was retrieved, but has been setup for a newer version of gcc. I think I remember seeing a post on the gentoo forums related to this, but don't take my word on it.
I haven't been too successful getting Gentoo running on my 166 either, but that's mainly due to network card issues. I didn't get to the point to choose which stage I wanted to install. Have you tried a stage 3 install? Do you really need that much of a performance perk on a 166? I guess this depends on the role the computer will play. And finally, have you searched or posted to the Gentoo forums? There's a wealth of information there... But, they do need a better search routine... HTH Shawn -----Original Message----- From: Aaron J. Seigo [mailto:[EMAIL PROTECTED] Sent: Sunday, November 02, 2003 1:25 PM To: [EMAIL PROTECTED] Subject: Re: (clug-talk) Gentoo Compile problemo -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 02 November 2003 11:07, Nick W wrote: > Setting it to 1 generated a whole new set of errors, but I still got out of > memory. > > ... > Out of Memory: Killed process 11849 (cc1) > gcc: Internal error: Terminated (program cc1) not knowing anything much about gentoo, there's a couple of reasons a compile can be running out of memory: a) it's simply compiling too much source all at once for the amount of RAM you have. rarely does this occur when compiling a single source file, since most people are sane enough to not make any single source file so egregiously large. however, some build systems, in a bid to save time, will #include a whole bunch of a source files into one file and pass that to the compiler; this obviously works not very well with large numbers of source files with not so much ram =) b) a compiler bug. i remember earlier in the year there was a buggy version of gcc in the FBSD ports collection that would run out of memory on certain (regular sized) source files in KDE, even on machines that had 512MB of RAM. it probably comes down to either the compiler being fed too much at once, or the compiler being buggy... - -- Aaron J. Seigo GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE/pWgF1rcusafx20MRAq74AKCZvVwxBdsSL5Gz9CYvLonp6NUYvQCeN4j9 +1Uo5fWEKvt0dB9ZZrBfEAA= =mJpL -----END PGP SIGNATURE-----
