[LLVMbugs] [Bug 15207] New: modules do not work with relative -I paths
bugzilla-daemon at llvm.org
bugzilla-daemon at llvm.org
Thu Feb 7 16:12:25 PST 2013
http://llvm.org/bugs/show_bug.cgi?id=15207
Bug ID: 15207
Summary: modules do not work with relative -I paths
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Frontend
Assignee: unassignedclangbugs at nondot.org
Reporter: richard-llvm at metafoo.co.uk
CC: llvmbugs at cs.uiuc.edu
Classification: Unclassified
$ mkdir bar
$ touch bar/foo.h
$ echo 'module foo { header "foo.h" }' > bar/module.map
$ echo '@import foo;' > foo.mm
$ clang foo.mm -Xclang -fmodules -I bar -c
<module-includes>:1:9: fatal error: 'bar/foo.h' file not found
#import "bar/foo.h"
^
1 error generated.
$ clang foo.mm -Xclang -fmodules -I $PWD/bar -c
$
I believe the problem is that we run the module compilation from within the
directory containing the module.map file, but the -I paths are relative to the
directory containing the original source file.
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20130208/ec8bda96/attachment.html>
More information about the llvm-bugs
mailing list