From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Zefram <zefram@fysh.org>
Cc: ZSH workers mailing list <zsh-workers@sunsite.auc.dk>
Subject: Re: PATCH: Re: dev-19 + latest patches: all Makefiles are rebuilt every time make is run
Date: Fri, 3 Mar 2000 18:41:01 +0000 [thread overview]
Message-ID: <1000303184101.ZM20924@candle.brasslantern.com> (raw)
In-Reply-To: <E12QwXl-000567-00@crucigera.fysh.org>
On Mar 3, 6:11pm, Zefram wrote:
} Subject: Re: PATCH: Re: dev-19 + latest patches: all Makefiles are rebuilt
}
} Bart Schaefer wrote:
} >+modules-bltin:: mymods.conf
}
} What's this double colon? It's very much not portable.
Eh? That's been legal in every "make" I've used since 1985. Where do
you know it to fail?
It tells "make" that there are different commands for the same target
when there are different dependencies. That is, normally if you write
target: dependency1
command1
target: dependency2
command2
You'll get either an error or something like
warning: overriding commands for target `target'
warning: ignoring old commands for target `target'
If you use a double colon, it means that "make" should execute command1
when dependency1 is out of date, and should execute command2 when
dependency2 is out of date, i.e. they're no longer mutually exclusive.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
prev parent reply other threads:[~2000-03-03 18:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-03 12:25 Andrej Borsenkow
2000-03-03 16:21 ` PATCH: " Bart Schaefer
2000-03-03 18:11 ` Zefram
2000-03-03 18:41 ` Bart Schaefer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1000303184101.ZM20924@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zefram@fysh.org \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).