[bug #63452] [Regression] --no-builtin-variables with --warn-undefined-variables trigger warning on MAKECMDGOALS

2022-12-24 Thread Paul D. Smith
Update of bug #63452 (project make): Status:None => Fixed Assigned to:None => psmith Open/Closed:Open => Closed Component Version:

[bug #63452] [Regression] --no-builtin-variables with --warn-undefined-variables trigger warning on MAKECMDGOALS

2022-11-30 Thread malcolm cook
URL: <https://savannah.gnu.org/bugs/?63452> Summary: [Regression] --no-builtin-variables with --warn-undefined-variables trigger warning on MAKECMDGOALS Project: make Submitter: malcook Submitted: Wed 30 Nov 2022 06:42:05

[bug #51306] Checking programming possibilities around “MAKECMDGOALS”

2022-08-30 Thread Paul D. Smith
Update of bug #51306 (project make): Status:None => Fixed Open/Closed:Open => Closed Fixed Release:None => SCM Triage Status:

[bug #51306] Checking programming possibilities around “MAKECMDGOALS”

2017-07-02 Thread Markus Elfring
Follow-up Comment #4, bug #51306 (project make): But the make rule set can be adjusted in some ways according to the query result. ___ Reply to this item at:

[bug #51306] Checking programming possibilities around “MAKECMDGOALS”

2017-07-02 Thread Paul D. Smith
Follow-up Comment #3, bug #51306 (project make): You can't change the set of goals that make will build by modifying the MAKECMDGOALS variable. All you can do is query which goals it will build. ___ Reply to this item at:

[bug #51306] Checking programming possibilities around “MAKECMDGOALS”

2017-07-02 Thread Markus Elfring
Follow-up Comment #2, bug #51306 (project make): I imagine that there is a need to express higher level requirements. If you know for example that parameter like “distclean” was passed somewhere in the list of make goals, I guess that it can make sense to omit the execution of previous targets wh

[bug #51306] Checking programming possibilities around “MAKECMDGOALS”

2017-07-02 Thread Paul D. Smith
= foo.c bar.c ifeq (,$(filter clean,$(MAKECMDGOALS))) include $(sources:.c=.d) endif will only include the files if "clean" doesn't appear anywhere in MAKECMDGOALS. However, I'm not sure that this is the correct behavior. Suppose someone used "make clean all"; no

[bug #51306] Checking programming possibilities around “MAKECMDGOALS”

2017-06-24 Thread Markus Elfring
URL: <http://savannah.gnu.org/bugs/?51306> Summary: Checking programming possibilities around “MAKECMDGOALS” Project: make Submitted by: elfring Submitted on: Sat 24 Jun 2017 10:22:36 PM CEST Severity: 3 -

Re: MAKECMDGOALS

2003-10-30 Thread Noel Yap
Are you executing gmake with a target (eg "gmake all") or relying on the "first rule hit" behaviour (eg "gmake")? If the former, what does "gmake -npqr all 2>&1 | grep MAKECMDGOALS" give? If the latter, I think MAKECMDGOALS is supposed to

Re: MAKECMDGOALS

2003-10-30 Thread Noel Yap
According to the NEWS file that comes with the source, MAKECMDGOALS was added in 3.76. HTH, Noel Andy Xiao wrote: > > I am executing gmake (verion 3.74) with a target: "gmake xxx", I am > expecting the MAKECMDGOALS containing xxx. > > At 05:20 PM 10/30/2003 -0500, N