I've never seen a Signal 11 failure that wasnt caused by hardware:

Once it was my Video card (in my PC) corrupting the bus.  This eventually
hosed the H/D beyond repair (I had to completely start over from the
disklabel).

Once it was a bad hard drive (errors on the sectors were getting
'repaired' wrong).

The 50000 times (approximately), it was bad RAM.

Dave


<quote who="Bruce O'Neel">
> Hi,
> Did you have any luck getting a really simple c program to build all the
> way?
>
> cheers
>
> bruce
>
> On Sun, Mar 21, 2004 at 03:17:18PM -0500, Michael Lesniak wrote:
>> I reinstalled comp.tgz because I was getting weird errors and nothing
>> would compile...
>>
>> Now, I try to install pkg_install,
>> # cd /usr/pkgsrc/pkgtools/pkg_install
>> # make
>>
>> and the last thing I see is, after it goes through its bit about the
>> vulnerabilities file not found and skipping vulnerability checking is:
>>
>> ===> Extracting for pkg_install-20040115
>> ===> Patching for pkg_install-20040115
>> cd /usr/pkgsrc/pkgtools/pkg_install/work/libnbcompat && /usr/bin/env
>> CC="gcc" ./confi
>> gure &&		/usr/bin/make
>> *** Signal 11
>>
>> Stop.
>> make: stopped in /usr/pkgsrc/pkgtools/pkg_install
>> *** Error code 1
>>
>> Stop.
>> make: stopped in /usr/pkgsrc/pkgtools/pkg_install
>> *** Error code 1
>>
>>
>> What could the problem be?  Why won't this old dog compile?
>> Should I scrap this whole NetBSD install and start over?
>>
>> Thanks,
>> mL
>>
>
> --
> edoneel@sdf.lonestar.org
> SDF Public Access UNIX System - http://sdf.lonestar.org
>


-- 
Dave Burgess
CTO and Chief Engineer, Nebraska On-Ramp
Bellevue, NE 68123