[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: autoconf-2.61's AC_LINK_IFELSE with MinGW cross-compilers

From: Eric Blake
Subject: Re: autoconf-2.61's AC_LINK_IFELSE with MinGW cross-compilers
Date: Mon, 02 Apr 2007 06:10:56 -0600
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20070221 Thunderbird/ Mnenhy/

Hash: SHA1

According to Chris Johns on 4/1/2007 11:57 PM:
>> I understand that MSYS
>> has a problem, but I don't know that Cygwin does.  Does Cygwin have
>> the problem?  If not, then the test is incorrect.
> It may have the problem if the file-system is FAT32 rather than NTFS. An
> RTEMS user reported Cygwin worked once he changed from FAT32 to NTFS.

On NTFS, Cygwin follows Linux and POSIX semantics.  On FAT32, the
underlying filesystem lacks mode bits, so there is no way to accurately
represent executable bits, so my understanding is that cygwin must fake
'test -x' by looking at extensions and she-bangs for regular files.  But
even then, it correctly marks FAT32 directories as searchable.  But FAT32
is inherently insecure, and the cygwin folks recommend against using it
(for example, the cygwin package of git will not work on FAT32,
intentionally choosing to require proper permissions provided by NTFS;
even though the upstream git maintainers have added a hack that blindly
bypasses file modes on cygwin on all filesystems because of the chance
that upstream maintainers felt that supporting FAT32 was worth their
while).  For the purposes of developing programs (and thus using
autoconf), I would hope that the developer is smart enough to realize the
limitations of FAT32 and develop on NTFS instead; but it does mean that
this autoconf test needs to actually test the feature of the current file
system rather than assuming global platform behavior.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at
Comment: Using GnuPG with Mozilla -


reply via email to

[Prev in Thread] Current Thread [Next in Thread]