RE: [build_w32.bat] feature request: add optional command line argument for executable name

2019-11-07 Thread Jannick
ult: 'gnumake') used at link time. Please feel free to edit and apply it. Thanks, J. >From 719d2337933e6e1d699c414a56689e34a00d078a Mon Sep 17 00:00:00 2001 From: Jannick Date: Tue, 5 Nov 2019 16:00:54 +0100 Subject: [PATCH 01/13] Windows build: regroup code blocks in build_w32

RE: [build_w32.bat] feature request: add optional command line argument for executable name

2019-11-03 Thread Jannick
Hi Eli, Many thanks for looking into this! On Sun, 03 Nov 2019 17:35:42 +0200, Eli Zaretskii wrote: > > From: "Jannick" > > Date: Sun, 3 Nov 2019 13:30:11 +0100 > > > > Would it be possible to pass to build_w32.bat in an optional command > > line argu

[build_w32.bat] feature request: add optional command line argument for executable name

2019-11-03 Thread Jannick
Hi, This is a pure Windows issue: Would it be possible to pass to build_w32.bat in an optional command line argument the executable name (currently hard coded in the variable MAKE as 'gnumake')? When creating a plugin (.dll) with GCC (by linking against gnumake.dll.a) which should then be called

RE: How to disable Guile?

2019-07-18 Thread Jannick
Hi Jeffrey, On Wed, 17 Jul 2019 20:55:48 -0400, Jeffrey Walton wrote: > I'm trying to build Make 4.2.1 from the release tarball on an antique system. > I've tried configuring with without a guile option, --without-guile and -- > disable-guile. In each case the tail of configure results in: > ./co

[PATCH] doc: escape @ in sample code

2019-06-27 Thread Jannick
Hi, this patch essentially escapes '@' in sample code such that '$@' (instead of '$') is printed. Patch file attached. diff --git a/doc/make.texi b/doc/make.texi index 01bcec7..75c8834 100644 --- a/doc/make.texi +++ b/doc/make.texi @@ -11275,7 +11275,6 @@ function in a file @file{mk_temp.c}: @ex

recipe line order not honored for $(foreach)

2019-06-27 Thread Jannick
Hi everybody, it appears that a $(foreach) statement appearing in any recipe line is evaluated before all remaining lines regardless where in the recipe it appears, then all remaining recipe lines are executed. I would expect the lines to be executed in the order of appearance. A simple culprit