On Fri, Dec 25, 2020 at 7:00 PM Jouke Witteveen wrote:
>
> * NEWS: Use "local" instead of the incorrect "lexically-scoped".
> * doc/make.texi: Refer to let/foreach variables as local variables.
> ---
> This is an erratum on the addition of $(let ...). During an early review
> of $(let ...), thutt
On Sun, 2020-12-20 at 14:19 -0900, Britton Kerin wrote:
> A while back there was talk about making Make a bit smarter about
> understanding implicit dependencies make-sphere stuff:
>
> http://gnu-make.2324884.n4.nabble.com/Idea-Add-COMMANDCHANGE-and-CACHE-td19133.html
>
> I've come to like the id
On Sun, 2020-12-20 at 18:09 -0500, Paul Smith wrote:
> I'm thinking of putting out a new release of GNU make early in the
> new year.
Hi all; just an update on this:
The company I work for was acquired, so I need to redo my disclaimer
with my new benevolent overlords. I've done this many times a
Follow-up Comment #10, bug #59956 (project make):
Using *otherwise* means that now if a recipe runs a program named *otherwise*,
it will start to fail whereas before it succeeded.
I'm really not jazzed about creating new esoteric syntax for this problem.
Anyway, adding new syntax doesn't really
Looks like the report in:
https://lists.gnu.org/archive/html/bug-make/2021-01/msg00016.html
... only this time without any version number. The answer a couple of weeks
ago was:
https://lists.gnu.org/archive/html/bug-make/2021-01/msg00017.html
(I couldn't find it with Google, even though I rem
Follow-up Comment #9, bug #59956 (project make):
What about mixing in the special *$* character to help with differentiation?
Or adding *[]* to denote *make* only syntax.
$[ifeq (1,0)]
$[info Maybe this could work with leading tabs also]
$[else]
$[info Or with whitespaces]
$[endif]
Be
On Thu, 2021-01-28 at 12:34 +, Niko's ProtonMail Account wrote:
> I think there may be a mistake in the section “5.8 Defining Canned
> Recipes” of the GNU Make manual:
> https://www.gnu.org/software/make/manual/make.html#Canned-Recipes.
>
> The examples show the “define” directive followed by
Dear GNU maintainers,
I think there may be a mistake in the section “5.8 Defining Canned Recipes” of
the GNU Make manual:
https://www.gnu.org/software/make/manual/make.html#Canned-Recipes.
The examples show the “define” directive followed by an equals sign (“=“),
however for me it only works on
Follow-up Comment #8, bug #59956 (project make):
i mean, the user would tell make through some option (a special target or even
presence of ".else" in the makefile) "this makefile uses .else, rather then
else". make then would not consider "else" a keyword.
The keyword does not have to be ".else".
> Consider the following example:
> ifeq (1,0)
> test:
> @if [ "asd" == "123" ]; then
> echo "true"
> else
> echo "false"
> fi
> endif
> The *else* recipe at line 5 is treated as part of the *ifeq (1,0)*
> conditional thus making the next re
10 matches
Mail list logo
