I hereby withdraw the issue with the OBJEXT/EXEEXT macros. It is still occuring somewhat reproducibly on one machine, but have not been able to reproduce it on another more vanilla Linux box. Further delving into the matter shows that even with the original configuration script it was trying to work out these macros.
Still rather confused about what was going on, especially as adding the macros and rebuilding configure seemed to resolve it. Whatever it is, it does seem to be isolated to my system, and fixed, so probably not worth bothering with. Sorry for the false alarm, but looked like it was more of a general problem at first. Tom Payerle Dept of Physics [EMAIL PROTECTED] University of Maryland (301) 405-6973 College Park, MD 20742-4111 Fax: (301) 314-9525
