[llvm-dev] Bootstrapping with in-tree libcxx

[Eric Fiselier via llvm-dev]

If you're willing to install libc++ you can easily work around this by
running `ninja install-cxx install-cxxabi` before running any of the LLVM
or Clang build targets.

/Eric

On Tue, Dec 27, 2016 at 7:45 AM, Carsten Mattner via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> On Tue, Dec 27, 2016 at 3:38 PM, Asiri Rathnayake
> <asiri.rathnayake at gmail.com> wrote:
> >
> >
> > On Tue, Dec 27, 2016 at 1:29 PM, Carsten Mattner via llvm-dev
> > <llvm-dev at lists.llvm.org> wrote:
> >>
> >> When I tried to build with -DLLVM_ENABLE_LIBCXX, I found out that
> >> it doesn't try to use the in-tree libcxx but looks for one built
> >> and installed in the system.
> >
> >
> > IIRC, -DLLVM_ENABLE_LIBCXX reduces to passing --stdlib=libc++ (see
> > [1]) to the compiler.
> >
> > What you can do is a two-stage build. On the first stage, build just
> > libc++ (ninja cxx cxxabi). On the second stage, re-configure with
> > -DLLVM_ENABLE_LIBCXX and build the rest of the tools. We have a
> > downstream builder that works this way to avoid a libstdc++ defect
> > on the host platform. I can't remember the exact details, can dig
> > them up if it helps.
>
> Yes please, that would be helpful as an interim workaround.
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20161228/aa4e23dd/attachment.html>