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

[G. Branden Robinson]

Hi Jacob,

Thanks for the quick response.

At 2024-12-01T23:48:09-0600, Jacob Bachmeyer wrote:
> On 12/1/24 21:03, G. Branden Robinson wrote:
> > [...]
> > 
> > So the "good tr" branch is being taken in the configure script, but not
> > in vivo at a shell prompt.  I can't explain this.
> 
> First question:  what shell is configure actually running under?
> 
> Autoconf makes an effort to find a plausible POSIX shell, and /bin/sh
> on Solaris 10 is not it.  The copy of bash-3.2 you used for
> interactive testing was probably not it either.  I seem to recall that
> grepping config.status for CONFIG_SHELL should tell you.

Here's what I get.

$ grep CONFIG_SHELL config.status
SHELL=${CONFIG_SHELL-/bin/bash}
  $as_echo "running CONFIG_SHELL=/bin/bash $*" >&6
  CONFIG_SHELL='/bin/bash'
  export CONFIG_SHELL

$ /bin/bash --version
GNU bash, version 3.2.51(1)-release (sparc-sun-solaris2.10)
Copyright (C) 2007 Free Software Foundation, Inc.

> Off the top of my head, try `CONFIG_SHELL=/full/name/of/bash-3.2
> configure` and see if the test works.

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.

> > 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?

Regards,
Branden

go
Description: Text document

signature.asc
Description: PGP signature