Hi Akim, On 7/10/19 9:32 PM, Akim Demaille wrote: > Hi Tim, > > Sorry I dropped the ball...
NP, I dropped it as well ;-)
>> 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?
It works as expected for mawk which effectively means the test is skipped.
>> 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").
I just summed up the man page and picked up the 'Do not ... print anything':
-q, --question
``Question mode''. Do not run any commands, or print anything;
just return an exit status that is zero if the
specified targets are already up to date, nonzero otherwise.
> So I'm just clueless here. I don't know what to do to address
> your issue.
It looks like this is not *my* issue. The issue shows up on different
installations which have gawk and make 4.2.1 in common.
I will check if the issue pops up with older make versions or with other
projects as well.
> Are you running "make syntax-check" on a configured builddir?
No sure what you mean. The command sequence to trigger the issue is
straight forward:
./bootstrap
./configure
make
make check
make syntax-check <- bang
What (C) project + environment are you using successfully ?
Regards, Tim
signature.asc
Description: OpenPGP digital signature
