It was just brought to my attention that the RPATH configuration isn't
uniform among the libraries produced by the release. Some use
$ORIGIN../lib/ and others have none. Is this by design? It seems like it
might be ideal for all of them to be configured the same way. If that
makes sense I'll cr
Isn't libc++.so dependent on libc++abi.so?
On Mon, Mar 5, 2018 at 10:30 AM, Jonas Hahnfeld wrote:
> From what I can see all of the libraries without RPATH are runtime
> libraries that are used by binaries compiled with Clang. I think they don't
> have a dependency on other libraries in that dire
https://bugs.llvm.org/show_bug.cgi?id=36595
Greg Clayton changed:
What|Removed |Added
Resolution|--- |WORKSFORME
CC|
> On Mar 4, 2018, at 12:03 PM, William Schmidt via lldb-dev
> wrote:
>
> Hello lldb devs,
>
> Hacking away at my lldb command history on macOS Darwin 10.13.3
>
> lldb -v =>
> lldb-900.0.64
> Swift-4.0
>
> I discovered that ESC-b moves the cursor one word to the left, while ESC-f
> moves
Ok, yes, you're right -- thanks for clarification.
On Mon, Mar 5, 2018 at 10:37 AM, Jonas Hahnfeld wrote:
> libc++.so should be a linker script that automatically pulls in libc++abi
> (see "Failed to read file header" in your output). And IIRC libc++abi is
> only one possible implementation that
