From: Joseph Myers <joseph@codesourcery.com>
To: "Maciej W. Rozycki" <macro@wdc.com>
Cc: <gcc-patches@gcc.gnu.org>, <libffi-discuss@sourceware.org>,
<golang-dev@googlegroups.com>, <zlib@gzip.org>
Subject: Re: [PATCH v2] Add `--with-install-sysroot=' configuration option
Date: Thu, 28 Nov 2019 21:06:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1911282102130.9015@digraph.polyomino.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.21.1911272204140.13542@redsun52.ssa.fujisawa.hgst.com>
On Thu, 28 Nov 2019, Maciej W. Rozycki wrote:
> >
> > Rather, it's a suffix (as in SYSROOT_SUFFIX_SPEC, no command-line option
> > to print it),
>
> Do you mean that there's no option to print SYSROOT_SUFFIX_SPEC on its
> own or that no option prints it as a path component? If the latter, then
> I think it's an awful shortcoming, because there's no reasonable way for
> a given GCC compilation to determine the layout expected.
There is no option to print the results of expanding SYSROOT_SUFFIX_SPEC
on its own. You can use -print-sysroot to print the full sysroot used,
including the suffix.
> Is it that with $toolexeclibdir we have say:
>
> /usr/mips64el-st-linux-gnu/
> +-> lib/
> | +-> 2e/
> | \-> 2f/
> +-> lib32/
> | +-> 2e/
> | \-> 2f/
> \-> lib64/
> +-> 2e/
> \-> 2f/
Yes.
> whereas `--sysroot=/path/to/sysroot' expects:
>
> /path/to/sysroot/
> +-> 2e/
> | +-> lib/
> | +-> lib32/
> | \-> lib64/
> \-> 2f/
> +-> lib/
> +-> lib32/
> \-> lib64/
Yes. This latter structure is currently one that GCC can *use* but never
*installs* anything into.
> If my understanding as expressed above is correct, then I think the way
> to move forward with this change will be to rename the option to
> `--with-toolexeclibdir=' or suchlike (and adjust documentation
> accordingly) so that it avoids the ambiguity of "sysroot" and is in line
> with the usual `--bindir=', `--libdir=', etc. or less usual
> `--with-slibdir=' options where people can adjust the various installation
> directories according to their requirements or preferences.
Yes, that seems a plausible approach.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2019-11-28 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 2:47 [PATCH] " Maciej W. Rozycki
2019-11-14 3:06 ` Joseph Myers
2019-11-18 2:04 ` [PATCH v2] " Maciej W. Rozycki
2019-11-19 0:11 ` Joseph Myers
2019-11-20 2:39 ` Maciej W. Rozycki
2019-11-20 17:46 ` Joseph Myers
2019-11-22 23:41 ` Maciej W. Rozycki
2019-11-22 23:54 ` Joseph Myers
2019-11-28 20:45 ` Maciej W. Rozycki
2019-11-28 21:06 ` Joseph Myers [this message]
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=alpine.DEB.2.21.1911282102130.9015@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=golang-dev@googlegroups.com \
--cc=libffi-discuss@sourceware.org \
--cc=macro@wdc.com \
--cc=zlib@gzip.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).