Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!munnari.oz.au!metro!dmssyd.syd.dms.CSIRO.AU!ditsydh.syd.dit.CSIRO.AU!evans
From: evans@syd.dit.CSIRO.AU (Bruce.Evans)
Newsgroups: comp.os.minix
Subject: Re: Thanks, but make still doesn't work!
Message-ID: <1991May10.111037.25776@syd.dit.CSIRO.AU>
Date: 10 May 91 11:10:37 GMT
References: <1991May10.035457.12570@mnemosyne.cs.du.edu>
Organization: CSIRO Division of Info Tech, Sydney, Australia
Lines: 20

In article <1991May10.035457.12570@mnemosyne.cs.du.edu> jhensley@isis.cs.du.edu (John 'Hawg' Hensley) writes:
>BUT... I tried chmem'ing make to just about every conceivable size, with
>no luck at all. It still gives an error 32512 on everything I try. If
>I could just find out what that means, it'd probably be easy to fix, but
>I can't find any references to it. If anyone has a clue, I'd greatly
>appreciate it. If nothing else, I suppose I could try reinstalling
>everything, but that seems a little extreme, as I haven't changed much 
>from the stock 1.5, and don't see how it would help.

32512 is 0x7F00. It says that some child process of make is returning the
code 0x7F. (This is an (irrelevant) bug in make. It does not really
understand U*x exit codes (sys/wait.h stuff). Make should report the error
code 0x7F too.)

0x7F is 127. 127 is what system() returns when it cannot execl /bin/sh.
Make calls system() a lot. It looks like /bin/sh is missing or is chmem'ed
too big to execute. I would expect a lot of other things to break if
/bin/sh is missing or nonstandard.
-- 
Bruce Evans		evans@syd.dit.csiro.au