-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Joey Mingrone on 4/30/2009 12:36 PM: >> ls -t "$srcdir/configure" conftest.file >> >> So, what "ls" is on the system, and is "ls" really /bin/ls or is it an >> alias? (I'm just paraphrasing the error message ;-) ) >> > > Yeah, /bin/ls is there, but it's not gnu ls. It does support the -t > option as well (sort by modified time). That's required by POSIX, and portable to VERY old systems. http://www.opengroup.org/onlinepubs/9699919799/utilities/ls.html > > I think I'm getting closer. I just moved /bin/ls out of the way and > put gnu ls in its place and configure ran without errors. Now to > figure out how to patch configure.in so it doesn't expect gnu ls. Or rather, how to detect broken ls that don't comply to POSIX. How likely is your broken ls to appear on other systems? In other words, is it a custom binary only likely to be on your machine, or is supplied by a vendor such that other people using the same vendor will hit the same problem? - -- Don't work too hard, make some time for fun as well! Eric Blake ebb9@xxxxxxx -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkn5+VcACgkQ84KuGfSFAYDtlwCeNKLXxfW1XU6xy/LDUA9yN90/ nTgAniUmapdvv7zdxfCr8R/ykl74Eh8o =rAGV -----END PGP SIGNATURE----- _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
