Re: stumped on a simple autoconf/m4/sh problem

On 12/2/24 00:47, G. Branden Robinson wrote:
> Hi Jacob,
>
> Thanks for the quick response.
I happen to be up late here.
> At 2024-12-01T23:48:09-0600, Jacob Bachmeyer wrote:
>> On 12/1/24 21:03, G. Branden Robinson wrote:
>>> [...]
> [...]
>
> Okay, I did.  The mystery would appear to deepen.
>
> The same grep gets the same results.
>
> I drive the build from a shell script because building on Solaris 10
> _or_ 11 is a headache.  I'm attaching the script.

Looking at the driver script, I now see that you are already giving 
configure CONFIG_SHELL=/bin/bash, presumably as a result of past 
problems.  (The "export CONFIG_SHELL=/bin/bash" line arranges this on 
Solaris 10.)

>>> Would someone kindly point out my rookie mistake?
>> I am not so certain that this is exactly a rookie mistake---it looks
>> like you may have uncovered a shell bug, but in which shell?
> I am baffled that bash 3.2 would behave one way interactively and
> another when run via configure.  Presumably something else is going on?

Your build driver script also prepends /usr/xpg4/bin to PATH; is there a 
"tr" in there?  Does your interactive PATH begin with that directory?


-- Jacob