bug#19579: Long lines, short awk

n tell, this was fixed as a side effect of Git commit 08849db8, made just ten days before my initial report. --Daniel -- Daniel Richard G. || sk...@iskunk.org My ASCII-art .sig got a bad case of Times New Roman.

bug#19579: Long lines, short awk

ot;rm" commands instead of a single giant invocation. (Moreover, even if $AWK didn't have a line-length limitation, the shell could still balk with an "Argument list too long" error.) IMO, it is better to have the distclean and maintainer-clean targets follow this same approach

bug#18744: Problem with am__is_gnu_make: Arg list too long

SION) here, as it is also defined" rather than "as it also" * "might cause the shell to die" rather than "might cause to die"? --Daniel -- Daniel Richard G. || sk...@iskunk.org My ASCII-art .sig got a bad case of Times New Roman.

bug#18744: Problem with am__is_gnu_make: Arg list too long

disc...@googlegroups.com gmake[3]: *** [test-suite.log] Error 1 gmake[3]: Leaving directory `/tmp/libarchive-3.1.2/_build' gmake[2]: *** [check-TESTS] Error 2 gmake[2]: Leaving directory `/tmp/libarchive-3.1.2/_build

bug#10237: AM_SILENT_RULES does not work with NonStop make

I just wish that these very real standards/implementation qualms had been addressed when AM_SILENT_RULES was originally developed. --Daniel -- Daniel Richard G. || sk...@iskunk.org My ASCII-art .sig got a bad case of Times New Roman.

bug#10237: AM_SILENT_RULES does not work with NonStop make

On Tue, 2011 Dec 6 16:15-0800, Paul Eggert wrote: > On 12/06/11 15:16, Daniel Richard G. wrote: > > > (Paul: Does $({}) work on NonStop?) > > I don't know, sorry. > > I wanted a solution that worked > on any POSIX platform -- POSIX 2008 says that > $(aaa${bbb}

bug#10237: AM_SILENT_RULES does not work with NonStop make

th are hard-coded to the make implementation detected at > configure time. I was vaguely aware of SET_MAKE, but I didn't know that using the same make program as configure detected was a basic premise of the system. I retract that critique, then. --Daniel -- Daniel Richard G. || sk...@iskunk.org My ASCII-art .sig got a bad case of Times New Roman.

bug#10237: AM_SILENT_RULES does not work with NonStop make

ace?) I don't mean to object to Paul's proposed solution in itself---it'll work for my needs just fine---but "nicer" and "consistent" seem to hold more sway in your reasoning here than robustness and efficiency. (Paul: Does $({}) work on NonStop?) --Daniel -- Daniel Richard G. || sk...@iskunk.org My ASCII-art .sig got a bad case of Times New Roman.

bug#9928: AM_SILENT_RULES breakage with old make(1)

ause they *work*. * The patch to address this issue touches only two lines of code. (See attached, against automake-1.11.1) --Daniel -- Daniel Richard G. || sk...@iskunk.org My ASCII-art .sig got a bad case of Times New Roman. Fix for http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9928 diff

bug#9928: AM_SILENT_RULES breakage with old make(1)

_CC = $(am__v_CC_$(V)) am__v_CC_ = $(am__v_CC_$(AM_DEFAULT_VERBOSITY)) to curly-braces-in-parens... AM_V_CC = $(am__v_CC_${V}) am__v_CC_ = $(am__v_CC_${AM_DEFAULT_VERBOSITY}) or parens-in-curly-braces... AM_V_CC = ${am__v_CC_$(V)} am__v_CC_ = ${am__v_CC_$(AM_DEFAULT_VERBOSITY)} ...then the variable references are processed correctly, and the silent- rules feature works as advertised. --Daniel -- Daniel Richard G. || sk...@iskunk.org My ASCII-art .sig got a bad case of Times New Roman.

bug#9306: Java build errors due to trailing colon in CLASSPATH

patch, which I will push > in a couple of days if there are no further comments. The patch works for me, and I defer to you on older shells being able to handle this. > BTW, are you the same "Daniel Richard G." listed in THANKS with the > address "dani...@teragram.com&q

bug#9306: Java build errors due to trailing colon in CLASSPATH

ttached is a tarball containing the minimal test case. --Daniel P.S.: Please Cc: any replies to me, as I am not subscribed to this list. -- NAME = Daniel Richard G. _\|/_Remember, skunks MAIL = sk...@iskunk.org (/o|o\) _- don't smell bad--- MAIL+= sk...@alum.mit.edu < (^),&

RE: Doesn't work: blah_PROGRAMS = $(EXTRA_PROGRAMS)

> -Original Message- > > Looks like automake is as confused as you are. For > now, here's a simple > workaround, using a helper variable that is not > special to automake: Oh, a workaround's not a problem; the bug is very narrow. In my case, I just assigned the same literal value to noin

RE: Doesn't work: blah_PROGRAMS = $(EXTRA_PROGRAMS)

> -Original Message- > > I don't think you need to use EXTRA_PROGRAMS if you > use the idiom > > bin_PROGRAMS = > if ENABLE_STUFF > bin_PROGRAMS += foo bar > endif That works too, but with EXTRA_PROGRAMS, you still get the targets---that is, you can still do "make

Doesn't work: blah_PROGRAMS = $(EXTRA_PROGRAMS)

ght I should bring it to the attention of this list. --Daniel -- Daniel Richard G. || dani...@teragram.com || Software Developer Teragram Linguistic Technologies (a division of SAS) http://www.teragram.com/

RE: Problem with sh "shift" command in config.status on HP-UX

> -Original Message- > > Thanks. It's this issue, fixed in current git (master > and branch-1-10): > patches/3344/focus=3347> Ralf, thank you for looking at that off-list. I've applied the patch in the referenced message, and the e

RE: Problem with sh "shift" command in config.status on HP-UX

> -Original Message- > From: bug-automake-bounces+oss=teragram@gnu.org > [mailto:bug-automake-bounces+oss=teragram@gnu.org] > On Behalf Of Ralf Wildenhues > > But how can this be. Just before the shift, one of > the two "set" > commands is executed and sets $1 to "x". Which is > e

Problem with sh "shift" command in config.status on HP-UX

/posix/sh autoconf 2.60 libtool 2.2.6 I'm reporting this against Automake because the problem cropped up on upgrading it. (Autoconf and Libtool have not been touched.) --Daniel -- Daniel Richard G. || dani...@teragram.com || Software Developer Teragram Linguistic Technologies (a division of SAS) http://www.teragram.com/