Date: Thu, 04 Jan 2001 15:34:17 +0000 From: Matthew Seaman <m.seaman@inpharmatica.co.uk> To: Neil Blakey-Milner <nbm@mithrandr.moria.org> Cc: Bill Fumerola <billf@mu.org>, Chris BeHanna <behanna@zbzoom.net>, FreeBSD-Stable <stable@FreeBSD.ORG> Subject: Re: Roadmap for perl upgrades to STABLE? Message-ID: <3A5497F9.728D6CA@inpharmatica.co.uk> References: <200012260828.eBQ8SFF09546@gratis.grondar.za> <Pine.BSF.4.21.0012270006380.2693-100000@browning.pennasoft.com> <20001226231547.R72273@elvis.mu.org> <3A547E37.846A303F@inpharmatica.co.uk> <20010104165613.A91031@mithrandr.moria.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Neil Blakey-Milner wrote:
>
> On Thu 2001-01-04 (13:44), Matthew Seaman wrote:
> > Bill Fumerola wrote:
> > >
> > > On Wed, Dec 27, 2000 at 12:08:53AM -0500, Chris BeHanna wrote:
> > >
> > > > Not that I'm a fan of the GPL, but wouldn't importation of gmake
> > > > into the toolchain that gets installed by default help this problem
> > > > along enormously?
> > >
> > > What can it do that bmake can't?
> > >
> >
> > Automatically generate dependencies and then apply them as part of a higher
> > level target all in the same `make' invocation? ie. `make depend' can be a
> > sub-target of `make all'. That's about the only feature of gmake I've ever
> > used and missed having in BSD make.
>
> all: .depend ?
>
> (that is to say, that's what it sounds like, I'm probably not parsing
> what you mean properly.)
Um... no. I don't think I explained myself clearly enough. The GNU make info
page says it like this:
> Generating Prerequisites Automatically
> ======================================
>
[talking about the use of `cc -M file.c'...]
>
> With old `make' programs, it was traditional practice to use this
> compiler feature to generate prerequisites on demand with a command like
> `make depend'. That command would create a file `depend' containing
> all the automatically-generated prerequisites; then the makefile could
> use `include' to read them in (*note Include::).
>
> In GNU `make', the feature of remaking makefiles makes this practice
> obsolete--you need never tell `make' explicitly to regenerate the
> prerequisites, because it always regenerates any makefile that is out
> of date. *Note Remaking Makefiles::.
and later on:
> How Makefiles Are Remade
> ========================
>
> Sometimes makefiles can be remade from other files, such as RCS or
> SCCS files. If a makefile can be remade from other files, you probably
> want `make' to get an up-to-date version of the makefile to read in.
>
> To this end, after reading in all makefiles, `make' will consider
> each as a goal target and attempt to update it. If a makefile has a
> rule which says how to update it (found either in that very makefile or
> in another one) or if an implicit rule applies to it (*note Using
> Implicit Rules: Implicit Rules.), it will be updated if necessary.
> After all makefiles have been checked, if any have actually been
> changed, `make' starts with a clean slate and reads all the makefiles
> over again. (It will also attempt to update each of them over again,
> but normally this will not change them again, since they are already up
> to date.)
Matthew
--
Certe, Toto, sentio nos in Kansate non iam adesse.
Dr. Matthew Seaman, Inpharmatica Ltd, 60 Charlotte St, London, W1T 2NU
Tel: +44 20 7631 4644 x229 Fax: +44 20 7631 4844
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A5497F9.728D6CA>