Subject: gcc fatal signal still desperately need help
To: None <port-mac68k@NetBSD.ORG>
From: Erich Rast <h0444zkf@rz.hu-berlin.de>
List: port-mac68k
Date: 04/11/1997 01:54:42
Hi,

I don=B4t want you to get bored, but i still haven=B4t been able to solve
my problem with gcc - it almost always exits with the error "cc1 got fatal
signal 4" or signal 11. This is what i=B4ve done so far to get things work:
1.) checked swap area - it=B4s 10meg, not enough for programs like dt? my re=
al
memory is 5meg (IIci)
2.) completely reinstalled the comp12 binaries on my zip (mounted on /zip)
3.) once again linked all new libexec (cc1, cc1plus etc.) to the correspondi=
ng
/usr/libexec/... on my root partition (hd 40meg)
4.) checked many, many gcc options e.g. i tried
     cc -I/dt-1.1.5 -I- -c grf.c
for this source for dt - because it still crashes i guess it=B4s not a
problem with symbolic links (grf.c only includes from his own directory no
system includes)
5.) read all manual pages corresponding to gcc, signals, devices (zip...), e=
tc.
6.) crashed my zip installation because i thought playing with disklabel wou=
ld
help improve the data security, repeated step 1-5 (i don=B4t longer think
this is a zip problem - something must be wrong with the gcc binaries on
_my_ configuration)

I don=B4t have to resources to do crosscompiling for NetBSD on another
system, so please don`t tell me i should recompile gcc.

Does anyone have any clue what the **** is wrong with my system?
Maybe it has something to do with the lack of an FPU?

Please, can anyone who knows this problem at least give me an hint how
to find it`s source or give me advice what i could check further?
- NetBSD is great, but without a C compiler it=B4s hmmm....blind? deaf?
If i only have to uppgrade to -current, that=B4s ok, but i don=B4t want to d=
o
this as long as i=B4m unsure if this solves the problem...

Yours,
       ---erich