Re: Problem building kdenetwork 3.3 on NetBSD 1.6.2

[Mark Davies <mark%mcs.vuw.ac.nz@localhost>]

On Friday 01 October 2004 00:08, Matthias Scheler wrote:
> Error code 127 means that the process exited because of a signal.
> There are three possible reasons which I can think of:
>
> 1.) Broken hardware, most likely broken memory.

Unlikely as this is happening in the 1.6.2 bulk build as well and to at least 
one other.

> 2.) The process hit the per process memory limit. You can add ...
>
>  UNLIMIT_RESOURCES+= datasize
>
>     ... to "pkgsrc/net/kdenetwork3/Makefile" to verify this theory.

I'm currently unable to easily test on a 1.6.2 system so I would really like 
to know if the above does (or doesn't) fix the problem.

> 3.) The system is running out of virtual memory. You could use your
>     favourite monitor utility (e.g. "top") to verify this.

see 1)

cheers
mark