[LLVMbugs] [Bug 13079] New: MSVC-built Clang cannot find VS headers in MSYS on x64 OS
bugzilla-daemon at llvm.org
bugzilla-daemon at llvm.org
Mon Jun 11 07:22:49 PDT 2012
http://llvm.org/bugs/show_bug.cgi?id=13079
Bug #: 13079
Summary: MSVC-built Clang cannot find VS headers in MSYS on x64
OS
Product: clang
Version: trunk
Platform: PC
OS/Version: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: Driver
AssignedTo: unassignedclangbugs at nondot.org
ReportedBy: vanboxem.ruben at gmail.com
CC: llvmbugs at cs.uiuc.edu
Classification: Unclassified
Clang built with MSVC using MSVC libs/tools under MSYS will allow to build
autotools projects in a MSVC-compatible way, which is one of the reasons Clang
is awesome.
Problem is: it seems Clang forgets about "Program Files (x86)" inside MSYS, and
searches these paths on my x64 Windows:
clang -cc1 version 3.2 based upon LLVM 3.2svn default target x86_64-pc-win32
ignoring nonexistent directory "C:/Program Files/Microsoft Visual Studio
10.0/VC/include"
ignoring nonexistent directory "C:/Program Files/Microsoft Visual Studio
9.0/VC/include"
ignoring nonexistent directory "C:/Program Files/Microsoft Visual Studio
9.0/VC/PlatformSDK/Include"
ignoring nonexistent directory "C:/Program Files/Microsoft Visual Studio
8/VC/include"
ignoring nonexistent directory "C:/Program Files/Microsoft Visual Studio
8/VC/PlatformSDK/Include"
#include "..." search starts here:
#include <...> search starts here:
m:/Development/x64-msvc/LLVM/bin/../lib/clang/3.2/include
End of search list.
>From regular cmd.exe, I get the working paths:
#include "..." search starts here:
#include <...> search starts here:
M:/Development/x64-msvc/LLVM/bin/../lib/clang/3.2/include
C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\Include
C:\Program Files\Microsoft SDKs\Windows\v7.0\Include
C:\Program Files\Microsoft SDKs\Windows\v7.0\Include\gl
End of search list.
I do not know where the difference comes from.
--
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the llvm-bugs
mailing list