There's some bash 3.2-related problem that causes configure to fail occuring on machines at anl and snl this week.
gfortran + bash 3.2.x + ubuntu == crash configure
in the fortran checks.
ubuntu 7.x has bash 3.2 and an extremely underpowered
default nonbash shell.
export CONFIG_SHELL=/bin/bash
./configure {with gfortran options}
this bug would be a fine opportunity to update
to the current babel fortran macros in the
chasm configure.
baallan@sandia.gov
Logged In: NO
additionally, there's an if test with "x" == "$var" (syntactically...)
where == is not allowed in shell if statements. should be =. this crashes pickier shells.
it should not be easily confused with an occurence of == in a C feature test when repairing...