Re: bin/53136: bmake evaluates MAKEFLAGS like command line argument

[Valery Ushakov <uwe%stderr.spb.ru@localhost>]

The following reply was made to PR bin/53136; it has been noted by GNATS.

From: Valery Ushakov <uwe%stderr.spb.ru@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: bin/53136: bmake evaluates MAKEFLAGS like command line argument
Date: Thu, 29 Mar 2018 15:13:08 +0300

 On Wed, Mar 28, 2018 at 17:40:01 +0000, Steffen Nurpmeso wrote:
 
 >   | On Tue, Mar 27, 2018 at 21:30:00 +0000, steffen%sdaoden.eu@localhost wrote:
 >   | 
 >   |> POSIX says for MAKEFLAGS
 >   |> 
 >   |> The difference between the contents of MAKEFLAGS and the make
 >   |> utility command line is that the contents of the variable shall not
 >   |> be subjected to the word expansions
 >   | 
 [...]
 >   | 
 >   |     read __ev__
 >  
 >  They do not survive the eval, yes.  I have committed a fix to
 >  where this comes from, we now simply ". FILE" dot include that.
 >  
 >   | so you end up with MAKEFLAGS that contains
 >   | 
 >   |     .MAKE.LEVEL.ENV=MAKELEVEL VAL_RANDOM=ssl arc4 builtin
 >   | 
 >   | it's just gmake treats those "arc4" and "builtin" differently, not
 >   | VAL_RANDOM assignment.
 >  
 >  That is the point, right.  gmake honours POSIX, bmake does not.
 >  With reproducer this time.  ^_^
 
 *What* is the point?  I can't see you making any.  Also, if i replace
 read+eval in your original example with dot-including the xxx.dat, I
 get
 
     VAL_RANDOM=ssl arc4 builtin
 
 in the output from stage3.  Do you expected something else?  Do you
 observe something else?
 
 -uwe