OK, thanks for the follow-up. Not everything makes sense yet but we are making progress.

Not to my knowledge. But let us state for the record what we have so far:

You try to run a configure script for a nondescript software using IBMs XlC compiler and you encounter a syntax error:

Code:

[...snipped...]
appending configuration tag "F77" to libtool
./configure[24690]: if:  not found
./configure[24690]: then:  not found
./configure[24692]: else:  not found
./configure[24694]: fi:  not found
./configure[24700]: if:  not found
./configure[24700]: then:  not found
./configure[24702]: else:  not found
./configure[24704]: fi:  not found
./configure[24707]: if:  not found
./configure[24707]: then:  not found
./configure[24714]: else:  not found
./configure[24720]: fi:  not found
./configure[24722]: case:  not found
./configure[24723]: syntax error at line 24723 : `)' unexpected
./configure[24723]: syntax error at line 19 : `)' unexpected

These configure-scripts are created automatically so a syntax error just because someone made a typo or so is quite unlikely.

Now my first question is if there might be something wrong with your environment: check /etc/environment of the system you compile at for anything unusual because the settings there are put into every processes environment. Next, remove any configuration files (~/.profile, ~/.kshrc, ~/.bashrc, ...., just rename them) and start a "blank" session with a minimal environment. Check this for any unusual stuff (i.e. weird aliases, redefined system commands and the like), set the minimum PATH necessary for compilation and try to run the configure script again.

Did you use the same configure-script in both the failed and the successful case or did you unpack the source into different directories? If the latter is the case: did all involved file systems have enough space or might some file have become truncated during the unpacking?

So far, these are my first ideas. I hope this helps.

bakunin