oddly enough, i told him this a few days ago, but he insisted that his
hardware was fine..
anyhow, thanks for the help you all have given me.
-- jan
On Wed, 26 Jan 2000, Chuck Robey wrote:
> On Wed, 26 Jan 2000, f.johan.beisser wrote:
>
> > ok, here's the scenario. I didn't install any ports until I went to do the
> > `make buildworld`, when I installed cvsup to get the source updates.
> >
> > full binary+sources install from the 14 Jan 2000 snapshot
> > AMD K6-2 450MHz (corroborated by dmesg output)
> > c. 8 gig Seagate IDE HD
> > 64 megs RAM
> > cheap motherboard with everything built in, and one PCI slot
> >
> > here is the final lines of output from trying to compile the GENERIC kernel
> > (doing a `/usr/sbin/config GENERIC`):
> > ---------------
> > -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2
> > ../../netinet/in.c
> > cc: Internal compiler error: program cc1 got fatal signal 11
> > *** Error code 1
> > cc: Internal compiler error: program cc1 got fatal signal 11
>
> Signal 11 is usually an artifact of bad hardware, like bad RAM. You don't
> state what version of FreeBSD he's running, either. Did you know that, if
> he's running a system older than about 3 months ago, he CAN'T buildworld
> unless he installs a new kernel first?
>
> ----------------------------------------------------------------------------
> Chuck Robey | Interests include C & Java programming, FreeBSD,
> [EMAIL PROTECTED] | electronics, communications, and signal processing.
>
> New Year's Resolution: I will not sphroxify gullible people into looking up
> fictitious words in the dictionary.
> ----------------------------------------------------------------------------
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
>
+-----// f. johan beisser //------------------------------+
email: jan[at]caustic.org web: http://www.caustic.org/~jan
"knowledge is power. power corrupts. study hard, be evil."
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
