[Top][All Lists]

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

Re: How to avoid the double execution of a make info call?

From: Martin Dorey
Subject: Re: How to avoid the double execution of a make info call?
Date: Thu, 22 Jun 2017 14:05:31 +0000

Your Makefile looks likely to rebuild .depend, a file that it includes.  So, like Paul said:

>> or else make has re-executed itself
>> because this makefile or one of its 
>> included files was rebuilt; see

On Jun 22, 2017, at 06:57, SF Markus Elfring <
address@hidden> wrote:

If you are seeing these values printed multiple times it means that the
makefile is being parsed multiple times.

How can such additional parsing be clarified further?

Will it help to display extra data from special make variables?

Why that might be, we can't determine from the information provided.

I hope then that the following test data can be better explained.

address@hidden:~/Projekte/Coccinelle/20160205/parsing_c> make clean

LEVEL 0: FLAGS : 7 modules without mli files
rm -f parsing_c.top

address@hidden:~/Projekte/Coccinelle/20160205/parsing_c> LANG=C make --no-builtin-rules V=1

LEVEL 0: FLAGS r: 8 modules without mli files
/usr/bin/ocamllex.opt lexer_c.mll
549 states, 26116 transitions, table size 107758 bytes
15973 additional bytes used for bindings
/usr/bin/ocamlyacc -v parser_c.mly
/usr/bin/ocamldep -one-line -I ../commons -I ../commons/ocamlextra -I ../globals -I  ../parsing_cocci *.mli *.ml > .depend

LEVEL 0: FLAGS r: 7 modules without mli files
/usr/bin/ocamlc.opt -unsafe -I ../commons -I ../commons/ocamlextra -I ../globals -I  ../parsing_cocci  -c token_annot.mli

It seems that a recursive make is not performed in this use case.


As always, if you can't figure out what's going on running "make -d"
will help you more than we can.

I wonder about the information “Re-executing[1]: make --no-builtin-rules -d” there.
Unfortunately, I do not recognise so far which rule triggers this action.

Which condition checks should I add?


Bug-make mailing list

reply via email to

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