[libcxx-dev] Problem installing libcxx and libcxxabi using Bootstrapping on Amazon Linux 2
Hasan Marzooq via libcxx-dev
libcxx-dev at lists.llvm.org
Wed Dec 15 00:50:51 PST 2021
"ldconfig -v" gives a huge output, so I've made it available via the link
below: It looks like path is available to ld.
https://drive.google.com/file/d/1iXZdvqmgNCs9My-CY-7VlkvKeYaeuSAG/view?usp=sharing
Let me know if you can't see?
Please don't get confuse between "/usr/local/lib/x86_64-unknown-linux-gnu"
and "/usr/local/lib/x86_64-unknown-linux" the difference of "-gnu" is
because when I don't give "-DLLVM_RUNTIME_TARGETS="x86_64-unknown-linux" in
cmake configure, then "-gnu" get added by cmake. So I know this and I've
stopped giving ""-DLLVM_RUNTIME_TARGETS="x86_64-unknown-linux".
Thanks!
On Wed, 15 Dec 2021 at 16:22, Raul Tambre <raul at tambre.ee> wrote:
> > Tried creating a symlink, but unfortunately getting the same error.
>
> Then it sounds like /usr/local/lib/x86_64-unknown-linux still isn't on
> ld's
> search path. Run the faulty linker command -v, which should print a bunch
> of
> info including the search paths.
>
> > (after doing "ninja-build -C build install-runtimes") ??
>
> install-runtimes only installs the runtimes (libc++, libc++abi and
> libunwind in
> your case). Use the regular install target for the rest.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/libcxx-dev/attachments/20211215/42d29b3a/attachment.html>
More information about the libcxx-dev
mailing list