This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH 2/4] Allow make-link-multidir to make subdirectories
- From: Palmer Dabbelt <palmer at dabbelt dot com>
- To: zackw at panix dot com
- Cc: libc-alpha at sourceware dot org, joseph at codesourcery dot com, schwab at linux-m68k dot org, patches at groups dot riscv dot org
- Date: Sat, 06 Jan 2018 12:12:18 -0800 (PST)
- Subject: Re: [PATCH 2/4] Allow make-link-multidir to make subdirectories
- Authentication-results: sourceware.org; auth=none
On Sat, 06 Jan 2018 07:04:45 PST (-0800), zackw@panix.com wrote:
On Sat, Jan 6, 2018 at 2:32 AM, Palmer Dabbelt <palmer@dabbelt.com> wrote:
The RISC-V Linux ABI doesn't define any libraries that go directly in
lib, instead they go into lib/ilp32 or lib/lp64.
Why did you invent a new convention for this, instead of using the
existing lib{32,64} or lib/<target-triple> conventions?
Sorry, the message was a bit truncated. We currently install libraries in the
following directories:
* lib32/ilp32: RV32 (the 32-bit ISA), with the 32-bit soft float ABI
* lib32/ilp32d: RV32, with the 32-bit hard float ABI
* lib64/lp64: RV64 (the 64-bit ISA), with the 64-bit soft float ABI
* lib64/lp64d: RV64, 64-bit hard float
we plan on eventually also supporting lib64/ilp32 and lib64/ilp32d (x32-style
ABIs).
The convention is slightly different because we wanted thing regular: we could
have picked something like "lib32" and "lib32/softfloat" (IIRC ARM does this),
but it seemed better to make thing orthogonal.