Paul Eggert wrote:
Anyway, if you can strace it (or whatever the equivalent of that is, on AIX), that will likely let us come up with a fix.
Well damn, after the reboot the problem seems to have disappeared, configure runs cleanly start to finish. (A colleague of mine requested the reboot, to clear up some "linker path problem" which suggests to me that we had some corrupted shared library or somesuch. I don't know why slibclean wouldn't have done the trick, but it didn't occur to me to ask for more details at the time.)
One thing I'm puzzled about. The AIX 5.1 documentation claims /bin/sh is the Korn shell; see <http://publibn.boulder.ibm.com/doc_link/en_US/a_doc_lib/cmds/aixcmds5/sh.htm>. Is that not true for you?
Yes, /bin/sh is hardlinked with /bin/ksh.
Also, is there anything unusual in your environment? E.g., what is the output of:
At this point, it just looks like a corrupted <something>. Sorry for the trouble.
-- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc OpenLDAP Core Team http://www.openldap.org/project/ _______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool
