similar to: Failed to replace stdlibc++ with libc++, linker phase error

On 04/12/2019 06:31 PM, Tom Stellard via llvm-dev wrote: > On 04/12/2019 04:28 PM, AiChi via llvm-dev wrote: >> Hi, >> >> I'm currently working on one of my team's project to build LLVM full clang toolchain (Clang, libcxx, libcxxabi) on a CentOS machine. >> >> Previously we compiled our codebase with llvm-toolset-7/clang++, which by default takes stdlibc++

Hello, I've some exceptions which I would like to solve to build LLVM+Clang from source on MacOSX 10.8+. " /Users/travis/build/vpmedia/crossbridge/llvm-2.9/lib/Transforms/Utils/CodeExtractor.cpp:728:28: [0;1;31m error: no matching constructor for initialization of 'std::vector<BasicBlock *>' std::vector<BasicBlock*> Succs(succ_begin(codeReplacer), " I

I'm stuck on 10.8.5 and got around it by: 1. Building the most recent stable branch of libc++. I got a couple of errors in the regression tests, but they looked like something obscure enough to net affect the compiler and so far, that is panning out. 2. I ran configure as follows: ../llvm/configure CXXFLAGS="-stdlib=libc++ -I/Programming/llvm/libcxx34/test/support

Hello, I have just built LLVM with CMake by following these instructions https://llvm.org/docs/GettingStarted.html#getting-started-quickly-a-summary and I am trying to run the regression tests using "make check-all" but there are some unexpected failures in libcxx and libcxxabi. Here's the test log: Expected Passes : 40745 Expected Failures : 258 Unsupported Tests : 1594

Trunk clang does not pass CMake C Compiler test like below: CMake Error at /home/usr4/c74014i/opt/cmake-3.16.3-Linux-x86_64/share/cmake-3.16/Modules/CMakeTestCCompiler.cmake:60 (message): The C compiler "/home/usr4/c74014i/opt/clang/current/bin/clang" is not able to compile a simple test program. It fails with the following output: Change Dir:

I've been unsuccessfully trying tell g++ or clang++ to use libc++(abi) when building a C++ source file (single file for test purposes) when the host cc and c++ are all configured to use glibc and libstdc++. My goal is to statically links musl libc and libc++(abi) and create binaries for Linux that just work anywhere. Naturally, I'm not building a .so or depending on dynamic libs. My last

[Sorry about the crosspost. Since this is a clang build question but the build is invoked from the top-level LLVM directory I'm not sure where the question should go.] I've got a clang build against libstdc++ on Linux but I would really like one built against libc++/libc++abi. In other words I'd like to rebuild clang/llvm with clang using libc++ and libc++abi on Linux. I looked at

Alpine linux is a distribution that uses musl libc instead glibc. Here are my steps to reproduce: On Alpine linux, download LLVM, Clang, LLD 6.0.0 from releases.llvm.org, and build them from source. $ clang -c hello_world.c $ ld.lld --gc-sections -m elf_x86_64 -o hello_world /usr/lib/gcc/x86_64-alpine-linux-musl/6.4.0/../../../../lib/Scrt1.o

This may be that the libgcc_s.dylib based unwinder is incompatible with the darwin unwinder. You cannot mix and match the two. One of the lines from the bugzilla comments shows: /sw/lib/gcc4.5/lib/libgcc_s.1.dylib (compatibility version 1.0.0, being used. That will not work. All of the libgcc_s.dylib functionality has been subsumed into libSystem.dylib on SnowLeopard (darwin10). The

Nick, How exactly do you envision this being done? Looking at the contents of config/darwin.h, I see... /* Support -mmacosx-version-min by supplying different (stub) libgcc_s.dylib libraries to link against, and by not linking against libgcc_s on earlier-than-10.3.9. Note that by default, -lgcc_eh is not linked against! This is because in a future version of Darwin the EH frame

I realize this is off-topic for the list, but I thought all the darwin developers here might want to be aware of this. The current regressions in gcc trunk regarding exception handling has been escalated to a P1 in order to attract darwin developers to the issue... http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41260#c31 If these regressions aren't fixed before gcc 4.5's release, it appears

Can you add `--reproduce=repro` to lld command line? That generates repro.tar in your current directory which contains all input files. And then please compress and upload it somewhere so that we can take a look. On Mon, Apr 2, 2018 at 9:18 AM Andrew Kelley via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Alpine linux is a distribution that uses musl libc instead glibc. Here are

https://superjoe.s3.amazonaws.com/temp/repro.tar.xz On Mon, Apr 2, 2018 at 1:26 PM, Rui Ueyama <ruiu at google.com> wrote: > Can you add `--reproduce=repro` to lld command line? That generates > repro.tar in your current directory which contains all input files. And > then please compress and upload it somewhere so that we can take a look. > > > On Mon, Apr 2, 2018 at

Hi folks! I'm trying to build LLVM with LLVM on Ubuntu using the commands below. Building it with the GNU stuff (cpp, gcc, g++ and binutils packages) works, but after removing it, moving LLVM to /usr/local and symlinking /usr/bin/ld to ld.lld, I'm getting the following: === snip === -- The C compiler identification is Clang 8.0.1 -- The CXX compiler identification is Clang 8.0.1 -- The

Please help me. How do I fix this bug @ubuntu:~/Documents/test$ clang hello.c -o hello /usr/bin/ld: cannot find crt1.o: No such file or directory /usr/bin/ld: cannot find crti.o: No such file or directory /usr/bin/ld: cannot find crtbegin.o: No such file or directory /usr/bin/ld: cannot find -lgcc /usr/bin/ld: cannot find -lgcc_s clang-2: error: linker command failed with exit code 1

1 hour ago I downloaded llvm-3.6.0-rc4-win32.exe from http://llvm.org/pre-releases/3.6.0/ . I tried to compile simple C code that just print "hello" , but it didn't compile , because clang.exe can't find . when I use clang-cl.exe with the same code , it worked . I also have the same problem with clang++ even with , I add -I flag to GCC (4.9.1) C++ headers , the result:

Re-adding the dev list. It's best to always keep the discussions on the list. Don't worry about the length of the message, you need to communicate the information that is important to describe your problem. So I am not the best person to answer this question since I don't build/test libcxx or libcxxabi, but I'm sure there are plenty of people on the list that are quite

On Sat, Jun 16, 2012 at 08:20:23PM +0900, Journeyer J. Joh wrote: > If the cross compiling is supported, is there any documentation on how to > do it? The short version is: assuming you have a cross-binutils installation using e.g. x86_64--netbsd-as and x86_64--netbsd-ld, you add a symlink called x86_64--netbsd-clang to clang and just call that with an appropiate --sysroot to make it find

Sorry for not explaining well. After compiling with g++-cross g++-cross -c a.c I do link using this command /gold_binutils/build/gold/ld-new -plugin ~/Desktop/Sanjeev/LLVM/llvm-2.7/Release/lib/libLLVMgold.so --eh-frame-hdr -melf_i386 -dynamic-linker /lib/ld-linux.so.2 /usr/lib/crt1.o /usr/lib/crti.o /usr/local/lib/gcc/i686-pc-linux-gnu/4.2.0/crtbegin.o

Hi all, I'd like to use LLVM 2.8 on a openSUSE 10.3 box and when I try to compile anything I get an error: martin at vm:~/project/backend> clang tutorial001.m -v -emit-llvm -o tutorial001 clang version 2.9 (trunk 122601) Target: x86_64-unknown-linux-gnu Thread model: posix "/usr/local/llvm/Debug+Asserts/bin/clang" -cc1 -triple x86_64-unknown-linux-gnu -emit-llvm-bc -disable-free