From: "François Pinard" <pinard@iro.umontreal.ca>
To: emacs-orgmode@gnu.org
Subject: Re: Reloading uncompiled and testing from several git branches
Date: Sat, 16 Feb 2013 19:08:35 -0500 [thread overview]
Message-ID: <86wqu7ajjw.fsf@iro.umontreal.ca> (raw)
In-Reply-To: <87vc9s1h9t.fsf@Rainer.invalid> (Achim Gratz's message of "Sat, 16 Feb 2013 15:10:22 +0100")
Achim Gratz <Stromeko@nexgo.de> writes:
> .PHONY: testclean # in case you'll ever have a file named "testclean"
> testclean: test clean
> In general all such targets that are simple combinations of existing
> teargets can be added that way.
Allow me a pedantic nit-pick, yet nothing so important in practice
nowadays.
Any Makefile which lists dependencies while expecting them to be
satisfied sequentially, one after another, is broken. Make does not
(theoretically) guarantee the order, while in practice, all "make"
programs I know satisfy dependencies from left to right.
In theory, still, "make" and "make -j4" (say) should yield the same
actions and effect. Automake-generated Makefiles respect this — or at
least, they once did, I did not check in a long while.
François
P.S. In fact, for the above reason and also for a flurry of other
reasons, often related to portability, almost all Makefiles are broken.
It is so difficult to get them right that an AM_MAINTAINER_MODE macro
has been added to Automake as a way to generate and sanctify incorrect
ones. A perfect Makefile is very rare.
next prev parent reply other threads:[~2013-02-17 0:08 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 20:19 Macro question with new texinfo exporter Thomas S. Dye
2013-01-29 18:21 ` Nicolas Goaziou
2013-01-29 18:49 ` Thomas S. Dye
2013-01-30 9:22 ` Bastien
2013-01-30 12:44 ` Nicolas Goaziou
2013-01-30 16:14 ` Bastien
2013-01-30 22:24 ` Nicolas Goaziou
2013-01-31 2:21 ` Thomas S. Dye
2013-01-31 13:51 ` Bastien
2013-01-31 13:58 ` Nicolas Goaziou
2013-01-31 21:23 ` Nicolas Goaziou
2013-02-04 15:43 ` Thomas S. Dye
2013-02-04 17:26 ` Bastien
2013-02-04 18:57 ` Achim Gratz
2013-02-16 9:21 ` Bastien
2013-02-16 10:19 ` Achim Gratz
2013-02-16 10:34 ` Bastien
2013-02-16 10:39 ` Achim Gratz
2013-02-16 13:18 ` Eric Abrahamsen
2013-02-16 13:23 ` Reloading uncompiled and testing from several git branches (was: Macro question with new texinfo exporter) Bastien
2013-02-16 14:10 ` Reloading uncompiled and testing from several git branches Achim Gratz
2013-02-16 14:21 ` Bastien
2013-02-16 14:59 ` Eric Abrahamsen
2013-02-17 0:08 ` François Pinard [this message]
2013-02-18 12:57 ` Nicolas Richard
2013-02-18 19:17 ` Achim Gratz
2013-02-19 1:17 ` François Pinard
2013-02-16 16:40 ` Macro question with new texinfo exporter Nick Dokos
2013-02-16 16:47 ` Nick Dokos
2013-02-16 16:19 ` Nick Dokos
2013-02-16 17:37 ` Thomas S. Dye
2013-02-04 18:10 ` Nicolas Goaziou
2013-02-04 18:48 ` Thomas S. Dye
2013-02-04 18:38 ` Achim Gratz
2013-02-04 20:21 ` Thomas S. Dye
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86wqu7ajjw.fsf@iro.umontreal.ca \
--to=pinard@iro.umontreal.ca \
--cc=emacs-orgmode@gnu.org \
/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.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).