#27 configure.in: use ${PATH}:, not $PATH:

[Jonathan Kamens]

When I configure cbb-0.9.5, I get warnings that look
like this:

checking for wish4.2... ../../src/cbb-0.9.5/configure:
test: too many arguments
no

I will attach a patch.

[Jonathan Kamens]

Patch for correct bash variable syntax in configure.in

[Brian Koontz]

Logged In: YES
user_id=28863

I'm not fully convinced the braces around $PATH are
necessary. There should be no reason for them, as the var
is simply part of a shell script, and /bin/sh doesn't have
a requirement for this syntax in the context used. Just
so I can rule out other problems, can you send me the
shell name/version you're using? I've tried this under
sh, bash, tcsh, and ksh, and do not see this warning.

--Brian

[Jonathan Kamens]

bash bug report

[Jonathan Kamens]

Logged In: YES
user_id=274776

You're right, the curly braces turn out to be necessary. I
thought they were because the problem went away when I added
them and ran autoconf, but in fact the problem went away
becuse I was using a newer version of autoconf which has a
workaround for the bash bug that's being tickled here.

You should upgrade to autoconf 2.13 and regenerate the
configure script with it to avoid this problem.

The problem occurs with bash 2 but not with bash 1. I will
attach the bug report that I just sent to the bash
maintainers.

[Jonathan Kamens]

Logged In: YES
user_id=274776

The maintainer of bash has convinced me that the behavior of
bash 2 is correct, so the right fix for this problem is to
upgrade to the current version of autoconf and rebuild the
cbb configure script with it.