make-3.82 NEWS question

2010-11-11 Thread Warren Dodge
In the NEWS file for make-3.82 is this info about the wildcard function * WARNING: Future backward-incompatibility! Wildcards are not documented as returning sorted values, but up to and including this release the results have been sorted and some makefiles are apparently depending on that

possible problem with $(dir ... )

2010-07-13 Thread Warren Dodge
I notice that $(dir ...) leaves the trailing / when given a full filename path. Is there an easy way to remove the trailing / ? It would nice to have a function that didn't leave it there in some applications we have. I tried to do this so I could get the root dir of a program, but it fails t

clarification the export VAR := VALUE

2010-06-17 Thread Warren Dodge
I am not sure if this is a bug report or an enhancement request. If I do the following Makefile # export TESTVAR := TEST $(shell xterm ) xterm: xterm ##

problem in using -j with make

2010-02-08 Thread Warren Dodge
I have a make file that is causing me a problem when I try to use the -j option to speed things up. Here is a simplified version of it that shows my problem. ### Makefile all:a b c d e touch all a b c d e: script.5files

Splitting lines problem in make-3.80 versus 3.81

2009-09-08 Thread Warren Dodge
I sent in a bug report the other day and got this as a response. > From make's NEWS file for the 3.81 release: > > * WARNING: Backward-incompatibility! > > In order to comply with POSIX, the way in which GNU make processes > backslash-newline sequences in recipes has changed. If your makef

Re: executing perl problem with make 3.81 versus 3.80

2009-09-03 Thread Warren Dodge
I'll check it out. Thanks ___ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make

executing perl problem with make 3.81 versus 3.80

2009-09-03 Thread Warren Dodge
I have this "Makefile.bug" and an empty file "yyy" which makes no logical sense as I stripped my original problem down to this. - touch yyy - M