search for: initheadersearch

Hi all, I think it's Gentoo's bug, but I want to know if anyone has the same issue here. I am compiling LLVM trunk on Gentoo (gcc 4.5.2), and I get error message below, --- make[4]: Entering directory `/nfs_home/chenwj/llvm-3.1/svn/build/tools/clang/lib/Frontend' llvm[4]: Compiling InitHeaderSearch.cpp for Release+Asserts build /nfs_home/chenwj/llvm-3.1/svn/llvm/tools/clang/lib/Frontend/InitHeaderSearch.cpp: In member function 'void<unnamed>::InitHeaderSearch::AddMinGWCPlusPlusIncludePaths(llvm::StringRef, llvm::StringRef, llvm::StringRef)': /nfs_home/chenwj/llvm-3.1/svn/llvm/to...

> /nfs_home/chenwj/llvm-3.1/svn/llvm/tools/clang/lib/Frontend/InitHeaderSearch.cpp:197:1: internal compiler error: in extract_insn, at recog.c:2103 I think that this is a GCC ICE. --Sean Silva On Wed, Sep 12, 2012 at 10:53 PM, 陳韋任 (Wei-Ren Chen) <chenwj at iis.sinica.edu.tw> wrote: > Hi all, > > I think it's Gentoo's bug, but I want to know if anyo...

See attachments: config.log Error on command line: llvm[4]: Compiling InitHeaderSearch.cpp for Release+Asserts build /home/jamitch/Downloads/llvm-3.2.src/tools/clang/lib/Frontend/InitHeaderSearch.cpp: In member function ‘void<unnamed>::InitHeaderSearch::AddMinGWCPlusPlusIncludePaths(llvm::StringRef, llvm::StringRef, llvm::StringRef)’: /home/jamitch/Downloads/llvm-3.2.src/tools/...

...Gentoo's bug, but I want to know if anyone has the same > issue here. I am compiling LLVM trunk on Gentoo (gcc 4.5.2), and I get > error message below, > > --- > make[4]: Entering directory `/nfs_home/chenwj/llvm-3.1/svn/build/tools/clang/lib/Frontend' > llvm[4]: Compiling InitHeaderSearch.cpp for Release+Asserts build > /nfs_home/chenwj/llvm-3.1/svn/llvm/tools/clang/lib/Frontend/InitHeaderSearch.cpp: In member function 'void<unnamed>::InitHeaderSearch::AddMinGWCPlusPlusIncludePaths(llvm::StringRef, llvm::StringRef, llvm::StringRef)': > /nfs_home/chenwj/llvm-3.1/s...

...want to know if anyone has the same >> issue here. I am compiling LLVM trunk on Gentoo (gcc 4.5.2), and I get >> error message below, >> >> --- >> make[4]: Entering directory `/nfs_home/chenwj/llvm-3.1/svn/build/tools/clang/lib/Frontend' >> llvm[4]: Compiling InitHeaderSearch.cpp for Release+Asserts build >> /nfs_home/chenwj/llvm-3.1/svn/llvm/tools/clang/lib/Frontend/InitHeaderSearch.cpp: In member function 'void<unnamed>::InitHeaderSearch::AddMinGWCPlusPlusIncludePaths(llvm::StringRef, llvm::StringRef, llvm::StringRef)': >> /nfs_home/chenwj/ll...

On Sep 12, 2012, at 8:50 PM, Sean Silva <silvas at purdue.edu> wrote: >> /nfs_home/chenwj/llvm-3.1/svn/llvm/tools/clang/lib/Frontend/InitHeaderSearch.cpp:197:1: internal compiler error: in extract_insn, at recog.c:2103 > > I think that this is a GCC ICE. Yes, very definitely. Jim > > --Sean Silva > > On Wed, Sep 12, 2012 at 10:53 PM, 陳韋任 (Wei-Ren Chen) > <chenwj at iis.sinica.edu.tw> wrote: >> Hi all, &gt...

Hi, I am compiling LLVm with clang and I get the following error: Compiling InitHeaderSearch.cpp for Release+Asserts build InitHeaderSearch.cpp:29:51: error: clang/Config/config.h : InitHeaderSearch.cpp: In member function ‘void<unnamed>::InitHeaderSearch::AddDefaultCIncludePaths(const llvm::Triple&, const clang::HeaderSearchOptions&)’: InitHeaderSearch.cpp:237: error: ‘C_INC...

...gt;>> issue here. I am compiling LLVM trunk on Gentoo (gcc 4.5.2), and I get >>> error message below, >>> >>> --- >>> make[4]: Entering directory >>> `/nfs_home/chenwj/llvm-3.1/svn/build/tools/clang/lib/Frontend' >>> llvm[4]: Compiling InitHeaderSearch.cpp for Release+Asserts build >>> >>> /nfs_home/chenwj/llvm-3.1/svn/llvm/tools/clang/lib/Frontend/InitHeaderSearch.cpp: >>> In member function >>> 'void<unnamed>::InitHeaderSearch::AddMinGWCPlusPlusIncludePaths(llvm::StringRef, >>> llvm::String...

Hi All, I am installing llvm 3.1 and clang from the source on my Mac os x 10.5.8. I got this error in the middle of the compilation process: llvm[4]: Compiling InitHeaderSearch.cpp for Release+Asserts build /Users/georgebaah/llvm3.1/llvm-3.1.src/tools/clang/lib/Frontend/InitHeaderSearch.cpp:29:10: fatal error: 'clang/Config/config.h' file not found #include "clang/Config/config.h" // C_INCLUDE_DIRS ^ /Users/georgebaah/llvm3.1/llvm-3.1.src/...

...a supported toolchain name in clang? We tend to need to hand-patch clang source to find include files properly on our systems, the patch looks something like this (just posting as a guideline, I'm not sure if this is the best approach or not, but it seems to work for us): Index: lib/Frontend/InitHeaderSearch.cpp =================================================================== --- lib/Frontend/InitHeaderSearch.cpp (revision 115972) +++ lib/Frontend/InitHeaderSearch.cpp (working copy) @@ -661,6 +661,19 @@ "x86_64-redhat-linux", "32", "&quot...

..... I build llvm/clang from trunk sources on OSX Lion 10.7.3 (i.e. x86_64-apple-darwin11.3.0 to speak GNU's platform-ese) where I also have successfully built a fsf-gcc 4.6.2 (and lately a 4.7 for that matter) from sources. Now, I think I understand that by playing with clang's lib/Frontend/InitHeaderSearch.cpp you can have clang use whatever libstdc++ include files you want. Is that really true and fully supported practice, or do you have, when on OSX, either stick with Apple's (through Xcode-)provided gcc 4.2.1's libstdc++ or the all-new (but still a bit immature) libc++? I'm aware (af...

The problem was solved by setting environment variable CXX. But somehow a new one came. The gcc is installed in /usr/local/gcc-4.2.3. I managed to change clang/lib/Frontend/InitHeaderSearch.cpp clang/lib/Driver/ToolChains.cpp to force clang use the crt lib for that version. For details, plz see http://www.advogato.org/person/redi/diary/228.html. So now I have no problem of using clang to compile a trivial C program of 20 lines. When I tried to compile programs of spec2006, such as...

...ectory ln: creating symbolic link `/usr/local/bin/clang++.exe' to `clang.exe': No such file or directory And similar errors. Running make with the -i argument finished the build, and I manually created the links. I don't think there were any other problems in the build, and I changed InitHeaderSearch.cpp as instructed for clang to locate the header files. clang managed to build my large (personal) project, forcing me to fix some syntax errors gcc allowed. Linking ran into a single multiple definition error: d:/super/dump/mingw/mingw/bin/../lib/gcc/mingw32/4.4.0/libstdc++.a(tinfo.o):C:\MinGW\...

...owing files: > > include/clang/Driver/HostInfo.h > lib/Basic/Targets.cpp > lib/CodeGen/TargetInfo.cpp > lib/Driver/HostInfo.cpp > lib/Driver/Tools.cpp > lib/Driver/Driver.cpp > lib/Driver/ToolChains.h > lib/Driver/Tools.h > lib/Driver/ToolChains.cpp > lib/Frontend/InitHeaderSearch.cpp > ... and maybe: > lib/StaticAnalyzer/Checkers/CheckSecuritySyntaxOnly.cpp > > It could be nice to add a target by just creating a target > configuration file (with everything in one file), maybe using plain > text files or tablegen. My guess is that many targets are simi...

Hi, Aaron > > I am not sure where to put cxxabi.h. How can I let clang find this > > header file while compiling LLVM and Clang (in step 2)? > > > > You need to add it to somewhere that is in Clangs includes search path. E.g. > $INSTALL/lib/clang/2.9/include perhaps. Thanks for your help. Now I have another problem, --- llvm[4]: Compiling Version.cpp for Release

...roblem to me is that clang should really pick the library under > /s/gcc-4.3.1/lib rather the one under /usr/lib/gcc. > > Is this a bug that clang does not pick the correct library path? Any > ways to fix this? From the top of my head, perhaps you can look into clang/lib/Frontend/InitHeaderSearch.cpp and try to use the GCC path you want. HTH, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science, Academia Sinica, Taiwan (R.O.C.) Tel:886-2-2788-3799 #1667 Homepage: http://people.cs.nctu.edu.tw/~chenwj

On Wed, Sep 12, 2012 at 08:52:08PM -0700, Jim Grosbach wrote: > > > On Sep 12, 2012, at 8:50 PM, Sean Silva <silvas at purdue.edu> wrote: > > >> /nfs_home/chenwj/llvm-3.1/svn/llvm/tools/clang/lib/Frontend/InitHeaderSearch.cpp:197:1: internal compiler error: in extract_insn, at recog.c:2103 > > > > I think that this is a GCC ICE. > > > Yes, very definitely. > > Jim Do you guys think putting Gentoo GCC 4.5 & 4.6 on the list is a good idea [1]? Regards, chenwj [1] http://llvm.or...

...these steps, I don't see clang in the bin directory: /home/avilella/src/llvm/latest/llvm/bin So I followed the instructions in the clang directory, and ran make -j8 on it: cd ~/src/llvm/latest/llvm-3.3.src/tools/cfe-3.3.src make -j8 Doing so, I get this clange/Config/config.h error: [...] InitHeaderSearch.cpp:17:51: fatal error: clang/Config/config.h: No such file or directory [...] This is mentioned in a bug report from 2011, which I would be solved by now: http://llvm.org/bugs/show_bug.cgi?id=11903 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.l...

...our C++ standard library headers. If Clang cannot find your system libstdc++ headers, please follow these instructions: - 'gcc -v -x c++ /dev/null -fsyntax-only' to get the path. - Look for the comment "FIXME: temporary hack: hard-coded paths" in clang/lib/Frontend/InitHeaderSearch.cpp and change the lines below to include that path. After I run 'gcc -v -x c++ /dev/null -fsyntax-only' at the terminal, the following error came up: ------------------- Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/i386-linux-gnu/gcc/i686-linux-gnu/4.5.2/lto-w...

On Mon, Sep 26, 2011 at 1:23 AM, Anton Korobeynikov <anton at korobeynikov.info> wrote: > Hello > >> How can I use the right triple? >> Thanks. > You're using the "right" triplet. However: > 1. Your system is unknown to driver (as shown in the warning) I'm looking into it. > 2. You need to "teach" driver to look for paths to the includes