From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: riscv@gentoo.org, Palmer Dabbelt <palmer@dabbelt.com>
Subject: Re: [gentoo-dev] How to structure our RISC-V support
Date: Fri, 07 May 2021 09:38:54 +0200 [thread overview]
Message-ID: <6184986d290358bcec30d8df6d39cd838d98b909.camel@gentoo.org> (raw)
In-Reply-To: <YJTbESCtPGhYcFzM@ofant>
On Fri, 2021-05-07 at 14:15 +0800, Yixun Lan wrote:
> On 22:30 Thu 06 May , Andreas K. Huettel wrote:
> > >
> > > Haven't I told you using two-level libdirs is stupid? So yes,
> > > please do that and let us be happy once again.
> > >
> > > That said, where does lp64gc land? Or isnon-multilib
> > > one-or-the-other the goal?
> >
> > It would be non-multilib one-or-the-other then for us.
> > The main relevant combination is rv64gc/lp64d, which is arguably what
> > a linux machine "should have".
> >
> > (I could also imagine to keep rv64imac/lp64 profile and stages (also
> > using lib64), these would have to mask stuff like rust then though.)
> >
> I'm fine with rust masked in lp64/other profile..
> but in my opinion: it's really up to upstream should fix/support it
>
> > (Unless Palmer et al come up with a fix for the libdirs on the
> > upstream side of things. Already e.g. libdir=lib64-lp64d would be much
> > easier to handle I suspect.)
>
> using one level path (eg. lib64-lp64d) won't fix the problem,
> the root cause is that we use a 'non-standard' lib path (QT5, Cmake issue),
> not matter it's one level or two level path, see bug here [1]
>
> [1] https://bugs.gentoo.org/781134
> https://gitlab.kitware.com/cmake/cmake/-/issues/22138
>
Maybe it doesn't matter for CMake but it does matter for us simpletons
who want '../' to work as its supposed to.
--
Best regards,
Michał Górny
next prev parent reply other threads:[~2021-05-07 7:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 20:01 [gentoo-dev] How to structure our RISC-V support Andreas K. Huettel
2021-05-06 20:16 ` Andreas K. Huettel
2021-05-06 20:16 ` [gentoo-dev] " Palmer Dabbelt
2021-05-06 20:16 ` [gentoo-dev] " Michał Górny
2021-05-06 20:30 ` Andreas K. Huettel
2021-05-06 20:34 ` Palmer Dabbelt
2021-05-07 16:11 ` Andreas K. Huettel
2021-05-07 6:15 ` Yixun Lan
2021-05-07 7:38 ` Michał Górny [this message]
2021-05-07 16:08 ` Andreas K. Huettel
2021-05-07 6:24 ` Yixun Lan
2021-05-07 16:05 ` Andreas K. Huettel
2021-05-08 12:42 ` [gentoo-dev] How to structure our RISC-V support -- Summary Andreas K. Huettel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6184986d290358bcec30d8df6d39cd838d98b909.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=palmer@dabbelt.com \
--cc=riscv@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox