From: Akim Demaille <akim.demaille@gmail.com>
To: "Tim Rühsen" <tim.ruehsen@gmx.de>
Cc: Paul Eggert <eggert@cs.ucla.edu>, Gnulib bugs <bug-gnulib@gnu.org>
Subject: Re: maintainer-makefile: catch uses of $< in non-implicit rules
Date: Wed, 10 Jul 2019 21:32:25 +0200 [thread overview]
Message-ID: <C8819A69-634B-4D64-A240-89EB62A86955@gmail.com> (raw)
In-Reply-To: <e9e5bdb1-e069-35d7-d8c2-66494182a280@gmx.de>
Hi Tim,
Sorry I dropped the ball...
> Reproducible everywhere (needs gawk being installed, else the
> sc_prohibit_gnu_make_extensions is a no-op).
Which is what I meant. So are you saying it work as (I) expected?
> Akim, at least with GNU make 4.2.1 the combination of -q and -p doesn't
> do what you expect. From the make man page, I would say that both
> options contradict. -q: don't print anything; -p: print the database
I'm using 4.2.1, and it does what I meant: -p prints the rules,
and -q (which is --question, not --quiet) avoids that we
fired a rule (i.e., "make -q" does not run "make all").
So I'm just clueless here. I don't know what to do to address
your issue.
Are you running "make syntax-check" on a configured builddir?
next prev parent reply other threads:[~2019-07-10 19:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-18 7:44 maintainer-makefile: catch uses of $< in non-implicit rules Akim Demaille
2019-05-18 7:52 ` Paul Eggert
2019-05-18 9:51 ` Akim Demaille
2019-05-18 18:21 ` Paul Eggert
2019-05-19 5:42 ` Akim Demaille
2019-06-17 9:57 ` Tim Rühsen
2019-06-17 9:59 ` Akim Demaille
2019-06-17 10:04 ` Tim Rühsen
2019-06-22 15:53 ` Akim Demaille
2019-06-24 9:42 ` Tim Rühsen
2019-06-24 15:56 ` Akim Demaille
2019-06-25 13:12 ` Tim Rühsen
2019-06-25 13:24 ` Tim Rühsen
2019-06-25 14:37 ` Bruno Haible
2019-06-25 14:39 ` Tim Rühsen
2019-06-25 14:46 ` Tim Rühsen
2019-07-10 9:07 ` Tim Rühsen
2019-07-10 9:38 ` Tim Rühsen
2019-07-10 10:21 ` Tim Rühsen
2019-07-10 19:32 ` Akim Demaille [this message]
2019-07-11 8:00 ` Tim Rühsen
2019-07-11 8:46 ` Tim Rühsen
2019-07-19 7:40 ` Bernhard Voelker
2019-07-19 7:30 ` Bernhard Voelker
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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C8819A69-634B-4D64-A240-89EB62A86955@gmail.com \
--to=akim.demaille@gmail.com \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=tim.ruehsen@gmx.de \
/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.
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).