Re: Fedora RISC-V port needs to put shared objects into /usr/lib64/lp64d

2024-04-30 Thread Andreas K. Huettel
Am Dienstag, 30. April 2024, 19:00:33 +11 schrieb Andrea Bolognani: > > Shouldn't the symlink point in the opposite direction anyway? > /usr/lib64/lp64d is the actual canonical path, /usr/lib64 is just for > compatibility. > > Though apparently (see elsewhere in the thread) Gentoo does it this >

Re: Fedora RISC-V port needs to put shared objects into /usr/lib64/lp64d

2024-04-22 Thread Andreas K. Huettel
> > Just for your information, here's how Gentoo is doing things to stay > compatible > with as many variants as possible: > PS. Stage files are here: https://www.gentoo.org/downloads/#riscv (rv32-ilp32 is still building, rv32 musl is waiting until the worst musl-1.2.5 issues are ironed

Re: Fedora RISC-V port needs to put shared objects into /usr/lib64/lp64d

2024-04-22 Thread Andreas K. Huettel
Hi, I'm handling the RISC-V libdirs in Gentoo. > There are multiple PRs and patches floating around that make RISC-V use > the /usr/lib64 directory, like other 64-bit ports. However, RISC-V > recommends to use /usr/lib64/lp64d for the Fedora ABI variant, and > various upstream projects follow