From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Nasrat Subject: Re: Elkscmd - 'make comb' fails on Debian Woody Date: Tue, 3 Sep 2002 13:55:09 +0100 Sender: linux-8086-owner@vger.kernel.org Message-ID: <20020903125509.GT25251@raq465.uk2net.com> References: <44632C76B97BD211AF6B00805FADCAB208790E45@exchange.saltaire.pace.co.uk> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <44632C76B97BD211AF6B00805FADCAB208790E45@exchange.saltaire.pace.co.uk> List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: "'Linux-8086@Vger.Kernel.Org'" On Tue, Sep 03, 2002 at 10:14:48AM +0100, Simon Wood wrote: > Hi all, > I had a moment last night where I decided to try out Elks (again - it's been > a long while since I last played). Grabed the cvs sources and it all built OK. Excellent, hopefully you'll find that the SIBO port still compiles and boots - if running out of memory rather quickly :) It works on the 3c at least :) > However 'make comb' failed quite drastically. It looks like the problem is > during the building of the '/dev' files. The script '/mnt/elks/dev/MAKEDEV' is > called, which calls '/bin/test'. The script in dev is designed for an elks system. Hadn't noticed before as SIBODEV is ok for creating the sibo port devices. > '/bin/test' does not exist on Debian ('/usr/bin/test' does though and a symlink Nor does it on RH/Mandrake. /usr/bin/test is from GNU sh-utils, but isn't used if your shell has a builtin test, eg bash. If we just used test in the script or moved to /usr/bin/test it would work in both ash/sash on elks and on a build machine. > Is there a fix to get away from this direct reference??? We can't use the actual > application from the Elks disk image (without the appropriate kernel module) > and we can't guarantee that they exist in those locations on the host machine. Hmm, is it wrong to assume that ppl developing elkscmd would have 1) a dev box they have root on 2) minix support in the kernel 3) binfmt_misc and binfmt_aout, and elksemu I know there are the DIRECT/RAMDISK methods of building elkscmd. It's probably easiest to ammend the script to use /usr/bin/test, althought the location is not guaranteed or does anyone know how using env with builtins is supposed to work. Paul