Date: Sun, 16 Jun 1996 20:35:45 +0000 From: bsd@mail.gld.com To: questions@freebsd.org Subject: (Fwd) Re: Why won't even the Generic kernel compile on 2.1.0 r Message-ID: <199606170040.UAA11976@mail.gld.com>
next in thread | raw e-mail | index | archive | help
------- Forwarded Message Follows -------
From: bsd@mail.gld.com
To: davidg@Root.COM
Date: Sun, 16 Jun 1996 20:29:38 +0000
Subject: Re: Why won't even the Generic kernel compile on 2.1.0 rele
Cc: questions@freebasd.org
Priority: normal
> > -I../.. -I../../sys -I../../../include -DGENERIC -DI586_CPU -DI486_CPU
> > -DI386_CP U -DSYSVMSG -DSYSVSEM -DSYSVSHM -DUCONSOLE -DBOUNCE_BUFFERS
> > -DSCSI_DELAY=15 -DCO MPAT_43 -DPROCFS -DCD9660 -DMSDOSFS -DNFS -DFFS
> > -DINET -DMATH_EMULATE -DKERNEL - Di386 -DLOAD_ADDRESS=0xF0100000
> > ../../kern/kern_synch.c cc: Internal compiler error: program cc1 got
> > fatal signal 4 *** Error code 1
> >
> > Stop.
> > digi3: {2}
> >
>
> The above is likely caused by either bad memory, bad cache RAM, or a
> CPU that is running faster than it should be. A "signal 4" is an illegal
> instruction trap.
>
> -DG
>
Ok, but I have since installed the newest SNAP on the same machine,
and everything compiles well with no hardware changes. If I notice
any other problems using SNAP I'll change the motherboard and SIMM
module first and see if that clears it up. Thanks for your help.
-Mike
Michael C. Shultz
President, MCS Computer Inc
DBA MCS Internet Services
309 North Spence Ave
Goldsboro, NC 27534
(919) 751-5777
email shultz@mail.gld.com
URL http://www.gld.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606170040.UAA11976>