Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!uunet!know!hri.com!spool.mu.edu!uwm.edu!ogicse!psgrain!hippo!ccml From: ccml@hippo.ru.ac.za (Mike Lawrie) Newsgroups: comp.unix.bsd Subject: Re: 386bsd: elvis won't compile Message-ID: <1992Sep13.212928.20072@hippo.ru.ac.za> Date: 13 Sep 92 21:29:28 GMT References: <1992Sep8.185716.23623@hippo.ru.ac.za> <BuA04M.J6H@ibmpcug.co.uk> Organization: Rhodes University, Grahamstown, South Africa Lines: 37 In <BuA04M.J6H@ibmpcug.co.uk> adrian@ibmpcug.co.uk (Adrian Hall) writes: >In article <1992Sep8.185716.23623@hippo.ru.ac.za> ccml@hippo.ru.ac.za (Mike Lawrie) writes: >>In /usr/src/usr.bin/elvis, I type "make" and end up with the message >> >> make: obj: No such file or directory >> >>There is a link /usr/src/usr.bin/elvis/obj->/usr/obj/contrib/elvis-1.5, >>but there is not even a directory /usr/obj/contrib. >> > mkdir -p /usr/obj/contrib/elvis-1.5 >Seriously though (sorry if I assumedyou didnt know the usage of the >mkdir command!), Yes, this clears the problem (many thanks), and indeed the mkdir command is very simple. The issue is to have the confidence that this is in fact the cause of the problem, and not something much more serious. It is not particularly obvious to me why the problem existed, surely the make should be able to do this automagically? The structure of the makefiles with .includes of mk files looks pretty complex to the uninitiated. If each time the make failed (including for some pretty serious reasons) then simple going around taking what might be wild shots at clearing the problem (eg deleting/creating files/directories) could wreck my installation. Thanks for your help - maybe someone will put this into the FAQ, as it is a pitfall for a beginner. Mike -- Mike Lawrie <ccml@hippo.ru.ac.za> Director, Computing Services ph +27 461 22023 x 279 Rhodes University, Drostdy Rd fx +27 461 25049 Grahamstown 6140, South Africa