-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Ralf Corsepius on 4/12/2007 10:43 AM: > On Thu, 2007-04-12 at 05:12 -0600, Eric Blake wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> According to Ralf Corsepius on 4/12/2007 4:46 AM: >>> To me this reads as: MinGW and Cygwin's "test -x" are broken. >> Give an example where cygwin's "test -x" is broken. > RTEMS users have reported it for both MinGW and for Cygwin. > > Cf. these are the Cygwin variant: > http://rtems.rtems.org/pipermail/rtems-users/2007-March/017888.html OK, thanks for the pointer - that mail is an example of a cross compiler, run on cygwin, but generating non-cygwin files and on a file system that lacks executable permission bits. It provides more proof that cross-compilers need not do the -x check, so the recent checkin that only turns off -x checking for cross-compilers was correct. I was more worried that you might have come up with an instance where a cygwin native executable test was failing. - -- Don't work too hard, make some time for fun as well! Eric Blake ebb9@xxxxxxx -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGHmam84KuGfSFAYARAsxtAJkBR6Py/dp/Z5ayDAMcbSOxGrKLgQCcD1yB 8UMSYPU98v1lIIlu+z9ES5M= =JGzO -----END PGP SIGNATURE----- _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
