From owner-cvs-usrbin Thu Sep 19 08:20:46 1996 Return-Path: owner-cvs-usrbin Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA20849 for cvs-usrbin-outgoing; Thu, 19 Sep 1996 08:20:46 -0700 (PDT) Received: from spinner.DIALix.COM (root@spinner.DIALix.COM [192.203.228.67]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA20681; Thu, 19 Sep 1996 08:20:10 -0700 (PDT) Received: from spinner.DIALix.COM (peter@localhost.DIALix.oz.au [127.0.0.1]) by spinner.DIALix.COM (8.7.6/8.7.3) with ESMTP id XAA27866; Thu, 19 Sep 1996 23:19:46 +0800 (WST) Message-Id: <199609191519.XAA27866@spinner.DIALix.COM> X-Mailer: exmh version 1.6.7 5/3/96 To: Nate Williams cc: CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-usrbin@freefall.freebsd.org Subject: Re: cvs commit: src/usr.bin/lex Makefile In-reply-to: Your message of "Thu, 19 Sep 1996 08:54:49 CST." <199609191454.IAA17919@rocky.mt.sri.com> Date: Thu, 19 Sep 1996 23:19:45 +0800 From: Peter Wemm Sender: owner-cvs-usrbin@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Nate Williams wrote: > > peter 96/09/18 22:21:12 > > > > Modified: usr.bin/lex Makefile > > Log: > > Clean up dependencies a bit (we were not doing a depend on scan.c) > > That's because we aren't required to do that unless we are > bootstrapping. Otherwise, the dependency is done below in the line. > > scan.o: parse.c Hmm, I see your point, but that still wasn't quite enough.. scan.o is also dependent on: /usr/include/stdio.h /usr/include/sys/types.h \ /usr/include/machine/ansi.h /usr/include/machine/types.h \ /usr/include/sys/cdefs.h /usr/include/machine/endian.h \ /home/src/usr.bin/lex/flexdef.h /usr/include/ctype.h \ /usr/include/runetype.h /home/src/usr.bin/lex/config.h \ /usr/include/string.h /usr/include/stdlib.h parse.h SRCS had parse.y in it, so that meant that parse.c (nor parse.y) was not having it's dependencies recorded either.. :-( > Nate I've been fighting with bmake for the last two weeks on several projects. Our bsd.*.mk files seem rather deficient in some areas and downright braindead in others. I am still yet to figure out how to get it to consistantly interpret .PATH:, and dependencies have been an utter joy. :-] Along the way, I've been looking a lot at how it's been done elsewhere in the tree and I've seen too much strangeness already. Aargh!!! I think I'm going insane. :-) Cheers, -Peter