Any getting these too?
ild-tools
cd /usr/src/bin/sh; make build-tools
cc -O -pipe -DSHELL -I. -I/usr/src/bin/sh -Wall -Wformat -c
/usr/src/bin/sh/mkinit.c
cc: Internal compiler error: program cc1 got fatal signal 11
Only people with dodgy memory or cache (probably memory).
--
Brian
Umm- doubt it, but I'll check. This system has been fine for the last 18
months and runs everything else just peachy.
On Wed, 26 Apr 2000, Brian Somers wrote:
Any getting these too?
ild-tools
cd /usr/src/bin/sh; make build-tools
cc -O -pipe -DSHELL -I. -I/usr/src/bin/sh -Wall
On Wed, 26 Apr 2000, Matthew Jacob wrote:
Umm- doubt it, but I'll check. This system has been fine for the last 18
months and runs everything else just peachy.
Sudden SIGSEGVs are almost always the result of failed memory. The fact
that the machine worked fine for 18 months doesn't mean
Any getting these too?
ild-tools
cd /usr/src/bin/sh; make build-tools
cc -O -pipe -DSHELL -I. -I/usr/src/bin/sh -Wall -Wformat -c
/usr/src/bin/sh/mkinit.c
cc: Internal compiler error: program cc1 got fatal signal 11
Only people with dodgy memory or cache (probably memory).
Or
Thanks to all who mentioned failing memory- I don't think this was the case.
Installing a new source tree on a local directory instead of building on
top of NFS mounted /usr/src worked for me.
It's not clear what to make of this.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
On Wed, 26 Apr 2000, Ron Klinkien wrote:
Any getting these too?
ild-tools
cd /usr/src/bin/sh; make build-tools
cc -O -pipe -DSHELL -I. -I/usr/src/bin/sh -Wall -Wformat -c
/usr/src/bin/sh/mkinit.c
cc: Internal compiler error: program cc1 got fatal signal 11
Only people with
Any getting these too?
ild-tools
cd /usr/src/bin/sh; make build-tools
cc -O -pipe -DSHELL -I. -I/usr/src/bin/sh -Wall -Wformat -c
/usr/src/bin/sh/mkinit.c
cc: Internal compiler error: program cc1 got fatal signal 11
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
