Re: makes which break with `silent-rules'

2009-05-30 Thread Thomas Dickey
On Sat, 30 May 2009, Ralf Wildenhues wrote: POSIX says that; however different implementations of 'make' treat forward-references differently. Well that's when you would put XY_V last, just to be sure: XY_ = unknown XY_0 = silent XY_1 = verbose XY_V = $(XY_$(V)) then there is no forward ref

Re: makes which break with `silent-rules'

2009-05-30 Thread Ralf Wildenhues
* Jan Engelhardt wrote on Wed, May 27, 2009 at 09:12:44PM CEST: > On Sunday 2009-05-24 15:24, Thomas Dickey wrote: > >> all : > >>echo $(XY_V) > >> > >> XY_V = $(XY_$(V)) > >> XY_0 = silent > >> XY_1 = verbose > >> XY_ = unknown > >> > >> I think this is supported by POSIX. POSIX [1] says: "Mac

Re: makes which break with `silent-rules'

2009-05-27 Thread Jan Engelhardt
On Sunday 2009-05-24 15:24, Thomas Dickey wrote: > On Sun, 24 May 2009, Bruno Haible wrote: > >>> - The `silent-rules' option enables Linux kernel-style silent build output. >>> This option requires the widely supported but non-POSIX `make' feature >>> of recursive variable expansion, >> >> We

Re: makes which break with `silent-rules'

2009-05-24 Thread Ralf Wildenhues
Hello Bruno, Bob, * Bruno Haible wrote on Sun, May 24, 2009 at 01:12:02PM CEST: > > - The `silent-rules' option enables Linux kernel-style silent build output. > >This option requires the widely supported but non-POSIX `make' feature > >of recursive variable expansion, > > We are talking

Re: makes which break with `silent-rules'

2009-05-24 Thread Thomas Dickey
On Sun, 24 May 2009, Bruno Haible wrote: - The `silent-rules' option enables Linux kernel-style silent build output. This option requires the widely supported but non-POSIX `make' feature of recursive variable expansion, We are talking about constructs like this: == Makefile ==

Re: makes which break with `silent-rules'

2009-05-24 Thread Ralf Wildenhues
sorry, hit the send key too early. * Ralf Wildenhues wrote on Sun, May 24, 2009 at 03:20:04PM CEST: > IRIX make barfs if the inner macro expansion is used without $() or ${} > even for one-character macros. IOW, IRIX make barfs over $(foo$V) but > copes with $(foo$(V)). There are also some make

Re: makes which break with `silent-rules'

2009-05-24 Thread Bruno Haible
> - The `silent-rules' option enables Linux kernel-style silent build output. >This option requires the widely supported but non-POSIX `make' feature >of recursive variable expansion, We are talking about constructs like this: == Makefile == all : echo $(XY_V) XY_V = $(X

Re: makes which break with `silent-rules'

2009-05-17 Thread Ralf Wildenhues
Hi Bob, * Bob Friesenhahn wrote on Sun, May 17, 2009 at 09:59:17PM CEST: > Is anyone aware of specific vendor make programs which fail with > automake 1.11's new `silent-rules' option? I don't know of any. Cheers, Ralf

makes which break with `silent-rules'

2009-05-17 Thread Bob Friesenhahn
Is anyone aware of specific vendor make programs which fail with automake 1.11's new `silent-rules' option? " - The `silent-rules' option enables Linux kernel-style silent build output. This option requires the widely supported but non-POSIX `make' feature of recursive variable expansio