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: Fri, 22 Nov 2019 23:54:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1911222345550.28545@digraph.polyomino.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.21.1911221935060.13542@redsun52.ssa.fujisawa.hgst.com>
On Fri, 22 Nov 2019, Maciej W. Rozycki wrote:
> As I recall the MIPS sysroot setup (please correct me if I got something
> wrong here) was like:
Yes, that's the sort of layout you get with sysroot suffixes. See
gcc/config/mips/{st.h,t-st} for an example.
> Then the right-hand side of /path/to/somewhere (except for usr/) is what
> gets printed by `-print-multi-directory' or the left-hand side of output
> from `-print-multi-lib', e.g. `sof/el/lib64' for the example above.
Rather, it's a suffix (as in SYSROOT_SUFFIX_SPEC, no command-line option
to print it), followed by a directory such as /lib64 that comes from
STARTFILE_PREFIX_SPEC. (Until MULTILIB_OSDIRNAMES /
-print-multi-os-directory were added, I think STARTFILE_PREFIX_SPEC was
the main mechanism for using directories such as /lib64; once the multilib
OS directory mechanism was added, STARTFILE_PREFIX_SPEC was needed much
less, but is still relevant for this sysroot use case, along with some
linker configuration in binutils to teach it about such directories.)
> Similarly `-print-multi-os-directory' prints a directory path relative to
> a lib/ subdirectory to the sysroot, so that would be `../sof/el/lib64'
> respectively.
Rather, it's a path relative to the (non-sysroot, before your patch)
directory where the compiler installs the libraries. See e.g. t-st using
paths such as ../lib64/2f.
> Well, I agree we need to have this stuff documented beyond what we
> currently have, but I think it applies equally to all the sysroot options
> we have, including both the `--sysroot=' GCC driver's option, and the
> `--with-sysroot=', `--with-build-sysroot=' and the newly-proposed
All three of those refer to the top-level sysroot path, to which a sysroot
suffix is appended based on SYSROOT_SUFFIX_SPEC (unless
--no-sysroot-suffix is used).
> `--with-install-sysroot=' `configure' script's options as well. All we
> currently have is this paragraph:
But this is a path relative to which SYSROOT_SUFFIX_SPEC isn't used at
all.
> And last but not least: do we want to hold my proposed change hostage to
> a sysroot handling documentation improvement? It does not appear fair to
> me as the situation with said documentation is not a new problem nor one
> specific to this newly-added option, and the new option merely played the
The proposed new option is, as far as I know, the first one introducing
this new kind of sysroot option (one for which the suffix from
SYSROOT_SUFFIX_SPEC is never added).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2019-11-22 23:54 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 [this message]
2019-11-28 20:45 ` Maciej W. Rozycki
2019-11-28 21:06 ` Joseph Myers
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.1911222345550.28545@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).