Re: newline escape problem.

[David Boyce]

At 12:53 AM 10/29/2002 -0500, Paul D. Smith wrote:
> Hmm.  Interesting.
>
> According to POSIX, setting the SHELL make variable has _NO_ effect on
> make's processing.  The POSIX definition of make requires that all
> commands be invoked "as if" passed directly to the system() function,
> and there is no way to specify that the system() function would use a
> different shell than the standard sh, of course.
>
> The standard handles SHELL specially such that it doesn't inherit that
> value from the environment nor put any make value for that variable back
> into the environment of subcommands, but neither does it provide for
> make to use the command provided by $(SHELL) rather than system() (or
> sh).

Paul,

Could you cite the relevant C&V please? I don't have access to POSIX.1 
(unless it's become freely available since I last looked?) but SUSv3 says 
only this:

     The SHELL macro shall be treated specially. It shall be provided by
     make and set to the pathname of the shell command language
     interpreter (see sh ). The SHELL environment variable shall not
     affect the value of the SHELL macro. If SHELL is defined in the
     makefile or is specified on the command line, it shall replace the
     original value of the SHELL macro, but shall not affect the SHELL
     environment variable. *Other effects of defining SHELL in the
     makefile or on the command line are implementation-defined.*

(emphasis mine). Does POSIX flatly contradict this? Surprising if true. And 
are you looking at a new or relatively old rev of POSIX?

-David