[LLVMdev] Can libc++ build for arm cross compiler?

gamma_chen gamma_chen at yahoo.com.tw
Wed Oct 1 02:36:11 PDT 2014

Logan and Richard,
Thank your quick and kindly help. I am busy with something else today and will try these script tomorrow.
Best regards

     Logan Chien <tzuhsiang.chien at gmail.com> 於 2014/10/1 (週三) 1:58 AM 寫道﹕

 Hi cschen,

Here are the test scripts which I written when I was developing ARM exception handling support:

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 (e.g. /usr/arm-linux-gnueabihf/include)
3. Compile with correct compiler/linker flags (e.g. -target arm-linux-gnueabihf and some cmake tricks)

Feel free to let me know if you have encountered any problem.


On Tue, Sep 30, 2014 at 5:22 PM, Richard Pennington <rich at pennware.com> wrote:

  On 09/30/2014 02:37 AM, gamma_chen wrote:
  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? 
 I use libc++ and libc++abi (as well as compiler-rt) for the ELLCC cross compilation tool chain project (http://ellcc.org). I use makefiles to build the libc++ stuff, which are pretty dependent on being used in an ELLCC environment. You can get pre built binaries from ftp://ellcc.org/pub. The tarballs contain pre built libraries for ARM (as well as Mips, x86, PowerPC, and semi-functional Microblaze).
LLVM Developers mailing list
LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20141001/6c337c4a/attachment.html>

More information about the llvm-dev mailing list