Folks, I'm trying to set up a libc++ buildbot on ARM and I found an inconsistency which I'm not sure how to fix. I got a build error like this: libc++abi.so: undefined reference to `_Unwind_GetGR' Since I expected that the symbol would be provided by that library, I searched the CMake on libc++abi and found this: option(LIBCXXABI_USE_LLVM_UNWINDER "Build and use the LLVM unwinder." OFF) ... if (LIBCXXABI_USE_LLVM_UNWINDER) add_subdirectory(src/Unwind) endif() But on the Libc++AndAbiBuilder, there's no way to set the CMake argument (or is there?): def getLibcxxAndAbiBuilder(f=None, env={}, additional_features=set()): "additional_features" seem to imply only lit test args, not anything else. Ideas? cheers, --renato
+Dan Albert On 10/20/14 4:53 AM, Renato Golin wrote:> Folks, > > I'm trying to set up a libc++ buildbot on ARM and I found an > inconsistency which I'm not sure how to fix. > > I got a build error like this: > > libc++abi.so: undefined reference to `_Unwind_GetGR' > > Since I expected that the symbol would be provided by that library, I > searched the CMake on libc++abi and found this: > > option(LIBCXXABI_USE_LLVM_UNWINDER "Build and use the LLVM unwinder." OFF) > ... > if (LIBCXXABI_USE_LLVM_UNWINDER) > add_subdirectory(src/Unwind) > endif() > > But on the Libc++AndAbiBuilder, there's no way to set the CMake > argument (or is there?):I *think* you can add "-DLIBCXXABI_USE_LLVM_UNWINDER" to the env argument and get what you want, but Dan will have to correct me on that...> > def getLibcxxAndAbiBuilder(f=None, env={}, additional_features=set()): > > "additional_features" seem to imply only lit test args, not anything else.They are lit test args, and triggers for -D defines for various weird configurations (e.g. single threaded). I don't think there is one for the unwinder (nor do I think it makes sense to add one for that). Cheers, Jon> > Ideas? > > cheers, > --renato > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >-- Jon Roelofs jonathan at codesourcery.com CodeSourcery / Mentor Embedded
> > But on the Libc++AndAbiBuilder, there's no way to set the CMake > argument (or is there?):No, there isn't. Should be simple enough to add though. I'd add it as a dict param. On Mon, Oct 20, 2014 at 8:11 AM, Jonathan Roelofs <jonathan at codesourcery.com> wrote:> +Dan Albert > > On 10/20/14 4:53 AM, Renato Golin wrote: > > Folks, > > > > I'm trying to set up a libc++ buildbot on ARM and I found an > > inconsistency which I'm not sure how to fix. > > > > I got a build error like this: > > > > libc++abi.so: undefined reference to `_Unwind_GetGR' > > > > Since I expected that the symbol would be provided by that library, I > > searched the CMake on libc++abi and found this: > > > > option(LIBCXXABI_USE_LLVM_UNWINDER "Build and use the LLVM unwinder." > OFF) > > ... > > if (LIBCXXABI_USE_LLVM_UNWINDER) > > add_subdirectory(src/Unwind) > > endif() > > > > But on the Libc++AndAbiBuilder, there's no way to set the CMake > > argument (or is there?): > I *think* you can add "-DLIBCXXABI_USE_LLVM_UNWINDER" to the env argument > and > get what you want, but Dan will have to correct me on that... > > > > def getLibcxxAndAbiBuilder(f=None, env={}, additional_features=set()): > > > > "additional_features" seem to imply only lit test args, not anything > else. > They are lit test args, and triggers for -D defines for various weird > configurations (e.g. single threaded). I don't think there is one for the > unwinder (nor do I think it makes sense to add one for that). > > > Cheers, > > Jon > > > > Ideas? > > > > cheers, > > --renato > > _______________________________________________ > > LLVM Developers mailing list > > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > > > > -- > Jon Roelofs > jonathan at codesourcery.com > CodeSourcery / Mentor Embedded >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20141020/2bc8e108/attachment.html>
Maybe Matching Threads
- [LLVMdev] Lib C++ buildbot problem
- Failed to configure LLVM for use with Musl
- Cannot compile LLVM suite with clang+lld
- Building LLVM with LLVM with no dependence on GCC
- [LLVMdev] RFC: Are we ready to completely move away from the optionality of a DataLayout?