On 3/3/21 4:05 PM, Ken Cunningham wrote:
As of clang-11, the most current libc++ is installed tucked away in
the llvm-11 libs dir.
There is both a dylib (rpathed) and a static libc++ there.
I set this up for now for people like you to use for exactly this. You
will have to force it (DYLD_LI
On 3/3/21 4:05 PM, Ken Cunningham wrote:
As of clang-11, the most current libc++ is installed tucked away in
the llvm-11 libs dir.
There is both a dylib (rpathed) and a static libc++ there.
I set this up for now for people like you to use for exactly this. You
will have to force it (DYLD_LI
As of clang-11, the most current libc++ is installed tucked away in the
llvm-11 libs dir.
There is both a dylib (rpathed) and a static libc++ there.
I set this up for now for people like you to use for exactly this. You will
have to force it (DYLD_LIBRARY_PATH, possibly static link it, or some ot
On Mar 3, 2021, at 03:59, Paul Floyd wrote:
> Hi
>
> A slightly off topic question. I have two macbooks, and the old one I use for
> testing the build of Valgrind when I'm wearing my opensource hat.
>
> The Mac is running 10.7.5. XCode for this platform is too old to build the
> current Val
