[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: win32 compilation of make 4.0 source code

From: Mark Brown
Subject: Re: win32 compilation of make 4.0 source code
Date: Tue, 28 Jan 2014 13:57:38 -0800

On Mon, Jan 27, 2014 at 11:05 PM, Mark Brown <address@hidden> wrote:
From: Paul Smith
Sent: Monday, January 27, 2014 8:57 PM
 ifneq ($(filter else-if,$(.FEATURES)),else-if)
   $(error Version $(MAKE_VERSION) does not support else-if)
Are you saying that this statement can be placed outside
of a make target recipe command sequence,
and would be executed before the target recipe command sequence ?
The answer to your question can be found in the GNU make info pages.

This is what the new make 4.0 manual says about -trace capability:
‘--trace’ Show tracing information for make execution. Prints the entire recipe to be
executed, even for recipes that are normally silent (due to .SILENT or 
Also prints the makefile name and line number where the recipe was defined,
and information on why the target is being rebuilt.

Again, this is a re-paste of the desired output,
which again you deleted in your reply:
$(CC) -c $(CFLAGS) $< -o $@
Make_filename     Makefile_Line_Num  auto_var_eval  auto_var_eval
/adir/bdir/cdir/Makefile554.mk  1177 make_debug.c  make_debug.o

In GNU make 4.0 the --trace option was introduced.  From the NEWS file:

 * New command line option: --trace enables tracing of targets.  When
Does this trace capability display the full evaluated automatic variables ?
Why not include a sample paste of its output.

You've been unwilling to given any specific examples of your problems,
makefile snippets, or output, and yet you question when other don't
provide them?  Since you obviously don't have the current version of
make installed, why would anyone bother?
Philip Guenther

Your role is maintenance of the make project.
It is not your role to solve other people's engineering problems.
When a bug or omission is presented to you, you have
at least 3 appropriate response options:
1) we do not think that is an issue that needs to be solved by make,
2) that issue needs to be solved in make, and it is, but in a different way
from what may be apparent from the documentation or intuitive,
Read the following link <URL, chapter, section> etc.
3) we do think that issue should solved by make, but it has
yet to be implemented.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]