Dear all,
as a follow-up, are there any plans to make lldb support CUDA, OpenCL or
SPIR-V based platforms in the near future?
Best,
P
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
-DLLVM_LIBDIR_SUFFIX=64 did the trick!
great -
Peter
On 03/16/2016 11:10 AM, Pavel Labath wrote:
This is just a wild guess, but could you try running cmake with
-DLLVM_LIBDIR_SUFFIX=64. I remember we've had a need for that in the
past for systems which store libraries in lib64. Some provisions w
This is just a wild guess, but could you try running cmake with
-DLLVM_LIBDIR_SUFFIX=64. I remember we've had a need for that in the
past for systems which store libraries in lib64. Some provisions were
put in place to autodetect it, but i'm not sure if they completely
work.
On 16 March 2016 at 10
Hi Pavel,
thank you for jumping on this thread and giving this honest answer. I
had a look at the build tree and indeed all binaries appear to be where
they should be, i.e. build/bin, build/lib* and build/lib64/python2.7
etc. I'll do as you suggest and copy them to their final destination for
Hi Peter,
thank you for the report, you are writing to the right list.
Unfortunately, I am not aware of anyone in LLDB, who actually uses the
"make install" functionality, so it's very well possible that it's
broken. I can take a look at it, but I won't be able to do that for a
couple of weeks no
Hi to all,
quick disclaimer: if this is the wrong mailing list, please let me know
and accept my apologies. But I am not sure, if this is a bug or just me
taking the wrong steps to build lldb. Feel free to suggest redirection.
I wanted to build the entire llvm 3.8 suite to explore some parall
