similar to: [LLVMdev] Correct usage of isysroot argument

Hi When I'm using clang 3.1 with the isysroot argument, it doesn't seem to pick up header files from the directory I'm passing through the command line: > $ clang -isysroot/myownheaders -v foo.c -c -o foo.o > clang version 3.1 (tags/RELEASE_31/final) > Target: i386-pc-linux-gnu > Thread model: posix > "/usr/bin/clang" -cc1 -triple i386-pc-linux-gnu -emit-obj

I'm do looking for the features the isysroot gives. I have "/myownheaders/usr/include" and "/myownheaders/usr/local/include" folders (they contain the actual header files). Again, the strange that gcc seem to be working with it. In the mean time I've found this (http://lists.cs.uiuc.edu/pipermail/llvmbugs/2011-December/021136.html), isn't it related? > From:

I have managed to compile llvm and clang against musl, but it behaves really strange: At first I tried to launch the compiler with musl dynamic loader: $ LD_LIBRARY_PATH=/path/to/musl/lib /path/to/musl/lib/ld-musl-x86_64.so.1 /path/to/llvm/bin/clang -v clang version 4.0.0 (https://github.com/llvm-mirror/clang 40adebeca0f99006d407508653c2cbd270a1a51c) (https://github.com/llvm-mirror/llvm

Hi Journeyer First, thank you so much for your updates on your experiments. I am currently following your steps but have found myself stuck with the following error: /usr/lib/gcc/arm-linux-gnueabi/4.6/../../../../arm-linux-gnueabi/bin/ld: this linker was not configured to use sysroots clang: error: linker command failed with exit code 1 (use -v to see invocation) I used the command string you

I am trying to build chromium and at this moment, They see some issues with internal one so recommended to use the flag -fno-integrated-as. Here is my exact build command (with -v and --save-temps): $ clang -Igen -I../../include -target aarch64-linux-gnu -march=armv8-a+crypto -fno-integrated-as --sysroot=./debian_jessie_arm64-sysroot -O2 -c MyFile.S -o MyFile.o -v --save-temps clang version

Dear all, I am not sure whether this is a right place to ask basic questions about usage of CLang/LLVM, but also not sure if there is any other mailing list for such. Kindly point me to such a list in such case. I had built mainline CLang/LLVM on OSX and tried to use it with CMake. I had override following variables in CMake:

On 08/02/13 14:42, Renato Golin wrote: [...] > Can you paste the result of a "clang -v -mcpu=CPU file.c" on your box? I > want to see what are the arguments and the assembler/linker it's > choosing to use. What CPU are we talking about? The box itself is an Allwinner A10; armv7l. /proc/cpuinfo says it's got swp half thumb fastmult vfp edsp neon vfpv3. I've been

Hello Gergö, Joerg and people on our list With your kind answer, I tried to build a hello world program for ARM(arm-none-linux-gnueabi) on my x86-64 PC. Thank you we verified the generated bitcode. The only thing remained is linking. Let me brief what I did so far. 1. Built Clang/llvm in a way explained in http://clang.llvm.org/get_started.html on Ubuntu 11.10 x86-64 PC 2. Downloaded gcc-4.0

Hello list. I wonder how I can make clang use specific linker. I am now trying to compile a hello world c code on an Ubuntu box for ARM and X86. And I have successfully built for ARM but NOT ABLE TO build one for X86. I am using a cross toolchain in the scratchbox environment of Tizen SDK. You can refer to the url below for my testing environment.

On 01/06/2013 07:20 PM, Dmitri Gribenko wrote: > On Mon, Jan 7, 2013 at 12:23 AM, Edward Diener > <eldlistmailingz at tropicsoft.com> wrote: >> On Mageia 2 I have installed the binary clang package clang3.0-7. When I >> tried to build the latest llvm/clang from source using this binary clang >> I get this error: >> >> 1) In file included from >>

Hello, I need to build a CLANG cross compiler for mips-linux-uclibc. To be completely compatible with the target system, I would like it to use linux 2.6.32.54 headers, binutils 2.25, gcc 4.1.2, and uClibc 0.9.30.1 for the gcc toolchain. I have been able to build the GCC toolchain a variety of different ways, but none of these builds can be "dropped in" via clang as a replacement for

Hello, am I wrong or the ARM c++ exceptions handling does not work? See the difference between assembly generated by clang and gcc with the following test code: #include <stdio.h> #include <exception> # test.cpp int main() { try { throw 20; } catch (int e) { printf("Exception Nr %d occurred\n", e); } return 0; }

Hi, I want to use LLVM 3.1 (with clang for the frontend) for compiling Open-MPI 1.6.3, which is a message-passing library. But I get a segmentation fault by the "Greedy Register Allocator". There is the bug # 11756 that solves a similar problem, but the bugzilla says "Version 3.0", and I am using 3.1 so it is likely a different bug that I am dealing with.

Hi! Quick question - do you know if recent commits could cause this error, or I should go to bisect/debug this? Do we have tests that check that -gsplit-dwarf succeeds (i.e. compile and link step work)? $ cat a.cc int foo(int x) { return x + 1; } int main() { return foo(42); } $ ./bin/clang++ -gsplit-dwarf a.cc /tmp/a-005b1a.o(.debug_pubnames+0x6): error: undefined reference to

Hi Ryan, Is there a PR about this? I've just hit the same assertion with AddressSanitizer, http://code.google.com/p/address-sanitizer/issues/detail?id=67 On Tue, Feb 14, 2012 at 2:57 AM, Ryan Taylor <ryta1203 at gmail.com> wrote: > clang: > /home/ryan/llvm/llvm_core/llvm-3.0/include/llvm/Support/Casting.h:194: > typename cast_retty<PHINode, ilist_iterator<Instruction>

clang: /home/ryan/llvm/llvm_core/llvm-3.0/include/llvm/Support/Casting.h:194: typename cast_retty<PHINode, ilist_iterator<Instruction> >::ret_type llvm::cast(const llvm::ilist_iterator<llvm::Instruction> &): Assertion `isa<X>(Val) && "cast<Ty>() argument of incompatible type!"' failed. 0 clang 0x0000000001b3618f 1 clang

Hi Alexander, I had the same error: sincos: /home/marcusmae/rpmbuild/BUILD/llvm/lib/VMCore/PassManager.cpp:635: void llvm::PMTopLevelManager::schedulePass(llvm::Pass*): Assertion `PI && "Expected required passes to be initialized"' failed. The solution was to add: PassRegistry &Registry = *PassRegistry::getPassRegistry(); initializeCore(Registry);

llvm[1]: Compiling APFloat.cpp for Release+Asserts build clang: TargetInfo.cpp:1778: llvm::Type *GetX86_64ByValArgumentPair(llvm::Type *, llvm::Type *, const llvm::TargetData &): Assertion `Lo->isIntegerTy() && "Invalid/unknown lo type"' failed. 0 clang 0x0000000001c132ef 1 clang 0x0000000001c13804 2 libpthread.so.0 0x00002ba7d7eaec60 3

Hello, Thank you for your kind attention to my issue and your help. I changed the tool chain and tried again. And there is a little progress but still have some problem. Using --sysroot doesn't make clang use linker(ld) in the cross tool. Most important question is how I can make clang use cross tool linker. Let me show you my experiment and questions below. There are two questions. [Run]

Dear Zhang, Compiler ends up invoking cc1 (the backend) anyways. So if you would like to invoke it by hand, the only thing to know is the right combination of options. Try to use the compiler verbose option "-v". It will show you how exactly clang invokes the backend: > clang -v -c showdebug.c clang version 3.2 (trunk 156703) Target: x86_64-unknown-linux-gnu Thread model: posix