Teach sandboxed GCC not to rely on inode numbers.

Inside the NaCl sandbox all inode numbers for files and directories are
identical (because the least common denominator, Windows, does not have them).

If GCC treats include directories (passed with -I) with identical inodes as
identical directories.  GCC then is free to skip looking into some directories
for header files as an optimization.  NaCl inodes are all identical, which makes
GCC to only look into a single directory.  Before we learn to emulate inode
numbers on Windows, the sandboxed GCC would just not use this optimization.

BUG=http://code.google.com/p/nativeclient/issues/detail?id=1362
TEST=none

Review URL: http://codereview.chromium.org/6685112
1 file changed