>> And many other errors coming from unknown items because of seemingly not >> or badly read include files. >> >> However the same line works fine if the project lies on a local drive. > > Have you tried adding "--save-temps" to your CFLAGS so that you can capture >the pre-processor output and take a look at the corruption? It might just >give us a clue.
I'm reviving this old thread in case somebody is looking for a solution. cpp.exe has a mechanism to ensure that the same file will not be included multiple times. It identifies "the same file" by remembering the device-id and inode-number of each already included file. Unfortunately, when the above problem happens, the inode numbers of different files are equal! That's why cpp.exe did just not include the second file and also didn't report any error... The issue about the non-unique inode numbers is described here: http://www.cygwin.com/cygwin-ug-net/highlights.html "On file systems which don't support unique persistent file IDs (FAT, older Samba shares) the inode number for a file is calculated by hashing its full Win32 path. The inode number generated by the stat call always matches the one returned in d_ino of the dirent structure. It is worth noting that the number produced by this method is not guaranteed to be unique. However, we have not found this to be a significant problem because of the low probability of generating a duplicate inode number." As gcc 3 and 4 don't have this problem they may do additional or different checks to not include a file twice. bye Fabi -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
