From: Yujie Yang <yangyujie@loongson.cn>
To: Xi Ruoyao <xry111@xry111.site>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH v1 1/6] LoongArch: a symmetric multilib subdir layout
Date: Mon, 14 Aug 2023 15:37:13 +0800 [thread overview]
Message-ID: <20230814073712.2eqs3p6s4xrykttm@loongson-pc> (raw)
In-Reply-To: <07a023290a898ba3e7a6ae1c36e6e4562bc66aaf.camel@xry111.site>
On Mon, Aug 14, 2023 at 01:38:40PM +0800, Xi Ruoyao wrote:
> On Mon, 2023-08-14 at 11:57 +0800, Yang Yujie wrote:
>
> > However, for LoongArch, we do not want such a "toplevel" library
> > installation since the default ABI may change. We expect all
> > multilib variants of libraries to be installed to their designated
> > ABI-specific subdirs (e.g. base/lp64d) of the GCC libdir, so that
> > the default ABI can be configured arbitrarily (with --with-abi)
> > while the gcc libdir layout stays consistent. This could be
> > helpful for the distribution packaging of GCC libraries.
>
> Have you tested a --disable-multilib configuration? To me with --
> disable-configuration everything should be still in the toplevel
> directory, not any sub-directory.
That's a good point, sorry I missed --disable-multilib here.
However, you don't really need --disable-multilib since
the libraries are only built once in the default ABI configuration
as long as --with-multilib-list does not request anything more than
that.
Maybe we should force-enabling multilib in all cases.
next prev parent reply other threads:[~2023-08-14 7:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 3:57 Yang Yujie
2023-08-14 3:57 ` [PATCH v1 2/6] LoongArch: improved target configuration interface Yang Yujie
2023-08-14 5:22 ` Xi Ruoyao
2023-08-15 1:12 ` Yujie Yang
2023-08-14 5:29 ` Xi Ruoyao
2023-08-14 5:58 ` Xi Ruoyao
2023-08-14 6:01 ` Xi Ruoyao
2023-08-14 8:44 ` Yujie Yang
2023-08-14 8:49 ` Xi Ruoyao
2023-08-14 8:57 ` Yujie Yang
2023-08-14 8:58 ` Xi Ruoyao
2023-09-06 6:43 ` Richard Sandiford
2023-09-06 6:54 ` Yang Yujie
2023-08-14 3:57 ` [PATCH v1 3/6] LoongArch: define preprocessing macros "__loongarch_{arch,tune}" Yang Yujie
2023-08-14 5:24 ` Xi Ruoyao
2023-08-14 3:57 ` [PATCH v1 4/6] LoongArch: use -mstrict-align by default when building libraries Yang Yujie
2023-08-14 5:18 ` Xi Ruoyao
2023-08-14 3:57 ` [PATCH v1 5/6] LoongArch: export headers for building GCC plugins Yang Yujie
2023-08-14 3:57 ` [PATCH v1 6/6] LoongArch: support loongarch*-elf target Yang Yujie
2023-08-14 5:38 ` [PATCH v1 1/6] LoongArch: a symmetric multilib subdir layout Xi Ruoyao
2023-08-14 5:40 ` Xi Ruoyao
2023-08-14 7:37 ` Yujie Yang [this message]
2023-08-14 7:48 ` Xi Ruoyao
2023-08-14 10:18 ` Yujie Yang
2023-08-14 11:16 ` Xi Ruoyao
2023-08-15 1:29 ` Xi Ruoyao
2023-08-15 2:32 ` Yujie Yang
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=20230814073712.2eqs3p6s4xrykttm@loongson-pc \
--to=yangyujie@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=xry111@xry111.site \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).