[cfe-commits] [patch] fix -include relative path .d file generation

[Nick Lewycky]

Hi,

There's a small difference between gcc and clang in emitted .d files when
-include was passed a relative path. Sadly, this actually breaks our build
system. GCC preserves what the user wrote in the argument while clang
replaces it with an absolute path. That breaks for us because we try to
relocate those files afterwards.

This moderately gnarly patch extends an existing hack to insert the file
specified in the -include path first, and any subsequent #include lookups
will find the same file with the first path is was looked up with.

Please review!

Nick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20110215/35665440/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pr8974.patch
Type: text/x-patch
Size: 8305 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20110215/35665440/attachment.bin>