In article <1992Aug18.001710.10722@sol.UVic.CA> pmacdona@sanjuan (Peter MacDonald) writes:[deleted] I was having that sort of problem myself, though I think it might have admitted to being the cpp getting the signal; anyway, something in gcc gets "fatal signal 11", so I gcc -E'd the file, same thing. So I looked and discovered that between the MCC 0.96 base distribution and the then-current MCC gcc disks, I had two different (diff: binariy files cpp and /lib/cpp differ) copies of cpp, so I moved one to cpp~, symlinked, and everything worked fine. I don't know why it started breaking, or what two cpp's were doing, but that fixed it. See if that's your problem too. Keith (rohrer@fncrd0.fnal.gov) -- Disclaimer: None of Grinnell College, URA, Fermilab, and any other affiliated persons or orginizations have licensed my ideas or opinions, and thus are not entitled to any which may appear above.
| Davide Libenzi | [patch 7/8] fdmap v2 - implement sys_socket2 |
| Greg Kroah-Hartman | [PATCH 018/196] coda: convert struct class_device to struct device |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| David Newall | Re: Slow DOWN, please!!! |
git: | |
| Christoph Lameter | Network latency regressions from 2.6.22 to 2.6.29 |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Arjan van de Ven | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
