Dmitry Goncharov wrote:
> > If a Makefile uses MAKEFLAGS=-r and
> > the Makefile in a subdirectory needs built-in rules, will the MAKEFLAGS=-r
> > setting propagate to the subdirectory?
>
> It will.
Ouch. This is usually undesired, since a developer works on one Makefile
at a time.
Together with
Dmitry Goncharov wrote:
> On Mon, Jul 17, 2023 at 5:45 AM Bruno Haible wrote:
> > And finally, MAKEFLAGS is not even mentioned in the main index of the GNU
> > Make
> > documentation [5], and only regarding "recursion" in the Variables index
> > [6].
>
> 5.7.3 contains
https://www.gnu.org/softw
On Mon, Jul 17, 2023 at 11:47 AM Paul Smith wrote:
>
> On Mon, 2023-07-17 at 11:45 +0200, Bruno Haible wrote:
> > Dmitry Goncharov wrote:
> > > Once the makefile author knows the makefile does not need built-in
> > > rules, they should add MAKEFLAGS=-r in the makefile and
> > > this will do a good
On 2023-07-19 03:49, Dmitry Goncharov wrote:
> On Mon, Jul 17, 2023 at 2:41 PM Alejandro Colomar
> wrote:
>
>> MAKEFLAGS += --no-builtin-variables
>
> If your makefiles are supposed to work on systems other than linux
> (still with gnu make), then you may need built-in variables.
> These variabl
On Wed, Jul 19, 2023 at 4:36 PM Jeffrey Walton wrote:
> SUFFIXES does not seem to work too well. 'make -d' still shows all the
> extra noise. For example, I added to the top of my GNUmakefile:
>
>.SUFFIXES: .h .c .cpp .S .o
>
> I still see:
>
> $ make -d -f GNUmakefile
...
> Trying implicit
