This is the mail archive of the
automake@gnu.org
mailing list for the automake project.
Re: envariable check still buggy
- To: François Pinard <pinard@iro.umontreal.ca>
- Subject: Re: envariable check still buggy
- From: Jim Meyering <meyering@ascend.com>
- Date: 27 May 1999 08:47:33 -0500
- Cc: Volker Borchert <bt@teknon.de>, automake@gnu.org
- References: <199905271100.NAA19202@Uranos.teknon.de> <87hfoybqz4.fsf@ascend.com> <oqu2syvdn0.fsf@titan.progiciels-bpi.ca>
François Pinard <pinard@iro.umontreal.ca> writes:
| Jim Meyering <meyering@ascend.com> writes:
|
| > | + * tests/Makefile.in: Put dependencies for check on a single
| > | + line to be sure they are checked and made in the right order.
| > | + The .env-warn file is in $(srcdir).
|
| > | -check: check-recursive
| > | +check: envvar-check check-recursive
|
| Hi, Jim, and people. I do not know how Automake currently stands with
| the loss of parallel-able Makefiles (which it once produced).
|
| I hope, Jim, after having convinced so many of us (:-), that you will
| stick to the idea that parallel make is a good thing, and do not commit
| modifications in a form that would prevent parallelism to work.
|
| If Automake gets repaired, it should not reveal that your Makefiles got
| broken in the meantime. Never ever give in broken Makefiles, neither for
| you or your installers (and whether maintainers or not :-). To rely on
| dependencies being made in sequence is abusing the semantic of Makefiles.
Hi François,
Sorry I wasn't clear. I was not advocating that particular change -- I
know full well it wouldn't have the desired effect with a parallel build.
As far as I know, automake rules are parallel safe/correct already.