Path: utzoo!utstat!helios.physics.utoronto.ca!jarvis.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!uunet!sci34hub!gary From: gary@sci34hub.UUCP (Gary Heston) Newsgroups: news.software.b Subject: Re: Peter's gripes Message-ID: <572@sci34hub.UUCP> Date: 3 Feb 90 01:53:55 GMT References: <519@smcnet.UUCP> <1990Jan30.041541.23578@elroy.jpl.nasa.gov> Lines: 29 In article <1990Jan30.041541.23578@elroy.jpl.nasa.gov>, david@elroy.jpl.nasa.gov (David Robinson) writes: > In article <1990Jan29.232907.12180@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes: > >Building such an interlocking set of makefiles, and making them portable, > >is really a good trick. We've never seen anyone do it particularly well. > [ ... ] Nothing should be passed on the make command line, > build should fixup the makefiles instead. Well, Dave, whip out your handy Shell Programming Guide, your Using make Handbook, sit down at your terminal, and go to it! Write away! Personally, I'm considering writing a (heavily) modified version of build that would remember the answer you gave it on the previous run. Before I do that, though, I have to get cnews running, and learn what I'm doing with it. I've gotten an error-free compile on my old Altos 586 (at home), and when I finish dealing with queuelen and spacefor here, I may know enough about it to start hacking a little. Maybe some code that would run test compiles to find out if the functions are there or not..... with that, build could answer some of the questions itself. > David Robinson elroy!david@csvax.caltech.edu ARPA -- Gary Heston { uunet!sci34hub!gary } System Mismanager SCI Technology, Inc. OEM Products Department (i.e., computers) Hestons' First Law: I qualify virtually everything I say.