similar to: [LLVMdev] question about llvm libc++ build

The following web say the libc++abi is ready on arm.http://libcxxabi.llvm.org/spec.html I try to build libc++ and libc++abi for host x86_64(linux) and target arm(linux) but fail.I have read the web http://llvm.org/docs/HowToCrossCompileLLVM.html Does anyone know whether it's available for my need? If you know how to build, what is the build options you use? Best regards cschen --------------

On Feb 3, 2015, at 1:40 PM, Duncan P. N. Exon Smith <dexonsmith at apple.com> wrote: > >> On 2015 Feb 3, at 13:26, Chris Bieneman <beanz at apple.com> wrote: >> >> >>> On Feb 3, 2015, at 1:06 PM, Jonathan Roelofs <jroelofs.lists at gmail.com> wrote: >>> >>> >>> >>> On 2/3/15 12:08 PM, Chris Bieneman wrote:

On 10/3/14 10:16 AM, Dan Albert wrote: >> >> I try to build libc++ and libc++abi for host x86_64(linux) and target >> arm(linux) but fail. >> > > Failing in what way? If this isn't working out of the box, we've done > something wrong. Yeah, it would help to know more specifics about where you're getting stuck. > > jroelofs might know more... For

Hi to all, when I download the clang/llvm officila binaries, I found the libc++ headers under lib directory, but I didn't found libc++.so. Why you ship libc++ headers but no shared library? Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131212/36204500/attachment.html>

Since the original buildit script doesn't cover my needs I switched to a custom but really similar script, in the meantime I also got the habit to dig for new flags and support and the __GLIBCXX__ define was hiding some of this errors. I see that other linux-based operating system offer this kind of support and they even use the same core components of my GNU/Linux distribution. You are

On 20.10.2012, at 22:47, Jordan Rose <jordan_rose at apple.com> wrote: > Hi, everyone. Today I was trying to build LLVM with libc++ and C++11 enabled, and I ran into this: > > http://stackoverflow.com/questions/10065384/instantiation-of-a-list-with-an-incomplete-type-in-a-typedef > > Basically, PBQP/Graph.h forward-declares classes, then tries to get iterators for

I think I've fixed this issue with r166484. Let me know if you run into further problems building PBQP with libc++ and C++11. - Lang. On Sat, Oct 20, 2012 at 2:59 PM, Lang Hames <lhames at gmail.com> wrote: > This is a known issue with the current PBQP data structures. I'm working > on an overhaul of the PBQP allocator at the moment which should address > this. > >

Hi, everyone. Today I was trying to build LLVM with libc++ and C++11 enabled, and I ran into this: http://stackoverflow.com/questions/10065384/instantiation-of-a-list-with-an-incomplete-type-in-a-typedef Basically, PBQP/Graph.h forward-declares classes, then tries to get iterators for std::lists of those classes. This is technically undefined behavior. I tried fudging with the order of

This is a known issue with the current PBQP data structures. I'm working on an overhaul of the PBQP allocator at the moment which should address this. - Lang. On Sat, Oct 20, 2012 at 2:08 PM, Benjamin Kramer <benny.kra at gmail.com>wrote: > > On 20.10.2012, at 22:47, Jordan Rose <jordan_rose at apple.com> wrote: > > > Hi, everyone. Today I was trying to build LLVM

Hello, since r243376 clang does not build with new libc++ anymore. Log attached. Reverting back lib/libc++ or not using libc++ fixes it. System: stable/9 amd64 r243742 WITHOUT_LIB32=yes WITHOUT_PROFILE=yes WITHOUT_SYSINSTALL=yes WITH_CLANG=yes WITH_CLANG_EXTRAS=yes WITH_CLANG_IS_CC=yes WITH_LIBCPLUSPLUS=yes CPUTYPE?=athlon64-sse3 CXXFLAGS+= -stdlib=libc++ -std=c++11 CC=clang CPP=clang-cpp

Hi Ioannis, If you only want the clang static analyzer, there is no need to check out and build libc++ as part of the process. The rest of the build can just use the system C++ library, which will be libstdc++ on Xubuntu. That said, without the full build log, it is hard to say what went wrong. Specifically, which references were undefined? -Dimitry > On 26 Mar 2016, at 16:04, Ioannis

Hi cschen, It seems that libunwind (the one included in libcxxabi) is mandatory at the moment. Use the second build command instead: $ CROSS_COMPILING=arm ENABLE_LIBUNWIND=1 ./scripts/compile-all.sh Logan On Tue, Oct 7, 2014 at 5:32 PM, gamma_chen <gamma_chen at yahoo.com.tw> wrote: > After do "sudo apt-get update", the following are pass. > > Install the

On Oct 8, 2009, at 4:52 PM, Stuart Hastings wrote: > Currently, to get LLVM to build "Apple-style," it's necessary to > copy two files (utils/buildit/GNUmakefile and utils/buildit/ > build_llvm) into the top-level directory. Why not: $ RC_ARCHS="x86" make echo Apple Build. Apple Build. $ make echo Standard Build Standard Build $ cat Makefile ifneq

Hello everybody, I am very new to llvm and I am struggling to install it on my 15.10 Xubuntu with kernel 4.2.0-34-generic #39-Ubuntu SMP x86_64 GNU/Linux. I essentially intend to use the clang static analyzer, but it seems that I have to build it on top of llvm and clang. Unfortunately I run into the following problem. CXX shared library ../../../lib/libc++.so at around 52% of the procedure

Hi Ioannis, Just delete the projects/libcxx directory, then rebuild from scratch. You should only need to checkout llvm (in the top level directory) and cfe (into the tools/clang subdirectory). -Dimitry > On 29 Mar 2016, at 00:08, Ioannis Koukoulis <i.g.koukoulis at gmail.com> wrote: > > Hi Dimitry, > > I do not particularly need to build libc++ from the package. Is the

On Oct 8, 2009, at 5:18 PM, Mike Stump wrote: > On Oct 8, 2009, at 4:52 PM, Stuart Hastings wrote: >> Currently, to get LLVM to build "Apple-style," it's necessary to >> copy two files (utils/buildit/GNUmakefile and utils/buildit/ >> build_llvm) into the top-level directory. > > Why not: > > $ RC_ARCHS="x86" make > echo Apple Build.

Hi cschen, Here are the test scripts which I written when I was developing ARM exception handling support: https://github.com/loganchien/libcxx-scripts The script should work on Debian wheezy (cross-compiling from amd64 to armhf.) In general, here are the necessary steps: 1. Get a working arm-linux-gnueabihf gcc/g++ toolchain (for the headers and libraries) 2. Setup the include search path

On Jul 10, 2007, at 10:41 PM, Chris Lattner wrote: > On Wed, 11 Jul 2007, Leo Fink wrote: >>> You need to build darwin driver to use -arch. Try using build_gcc >>> script to configure and build llvm-gcc. >> >> Well, I guess this task exceeds my expertise. I just thought there >> was some obvious mistake I made because a lot of people might be >> using

Hi Dimitry, this definitely worked. I am passed by the linking errors regarding libc++ or similar. My build stopped now at 95% while linking a clang extra, I am not pretty sure which because i do not have my laptop, possible the clang-rename, if such exists. No undefined references here, however, my hdd's free space run out, so this might be the cause. I have to move or expand now, alas!! The

Currently, to get LLVM to build "Apple-style," it's necessary to copy two files (utils/buildit/GNUmakefile and utils/buildit/build_llvm) into the top-level directory. This is generally a PITA inside of Apple. (I'll spare you the gory details. :-) I'd like to fix this for Apple, and I want to avoid compromising anybody else's build system. I've never used