[cfe-dev] [3.5 Release] test-release.sh intended behaviour (was <cxxabi.h> not found by clang-3.5 rc1 with libc++)
danalbert at google.com
Tue Aug 19 16:39:39 PDT 2014
libc++abi only has a cmake build system at this point (and lib/buildit, but
I like to pretend that doesn't exist), so it won't work with the
./configure build system (which test-release.sh uses). In addition, any
changes to the libc++ build system have been happening only in cmake (the
makefile in there is apple specific).
I didn't actually know test-release.sh existed before you started sending
mail about it, but if I had to guess I'd say it isn't used on Linux (not
with libc++, anyway).
Adapting test-release.sh to be able to use cmake is probably the right way
On Tue, Aug 19, 2014 at 3:51 PM, Renato Golin <renato.golin at linaro.org>
> On 17 August 2014 08:40, Ben Pope <benpope81 at gmail.com> wrote:
> > I'm currently thinking of adding
> > -enable-libcpp Use libc++ if available. [default: disable]
> > -use-cmake Use cmake build system instead of make.
> > To test-release.sh
> Hi Ben,
> I can't really help you, since I'm not yet at the stage where I care
> much about libc++ on ARM Linux, since I'm still fighting with
> compiler-rt and CMake builds on buildbots, but I will very soon care
> about it very seriously.
> I'd love to see such flags to test-release, and others that would make
> sure compiler-rt is properly compiled (using CMake) and put on the
> right path, and that libc++abi (which is required for unwinding) is
> correctly placed on a lib dir.
> For compiler-rt I had to fudge Clang to also add libgcc_s and
> libgcc_eh for now, but if we also have libc++abi we really can't be
> adding them. That's not done and will probably break. Could this be
> what's giving you trouble?
> Anyway, keep me in the loop of your CMake/libc++ adventures, as I'll
> be checking it soon.
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cfe-dev