From: Ian Lance Taylor <iant@golang.org>
To: "Maciej W. Rozycki" <macro@wdc.com>
Cc: Joseph Myers <joseph@codesourcery.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
libffi-discuss@sourceware.org,
gofrontend-dev <gofrontend-dev@googlegroups.com>,
zlib@gzip.org
Subject: Re: [committed v4] Add `--with-toolexeclibdir=' configuration option
Date: Fri, 24 Jan 2020 14:36:00 -0000 [thread overview]
Message-ID: <CAOyqgcXVUoc7E521w1bgP7=OxA9WABs=VzK_uNhp=2QggrOCfg@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.21.2001241045570.14118@redsun52.ssa.fujisawa.hgst.com>
On Fri, Jan 24, 2020 at 3:27 AM Maciej W. Rozycki <macro@wdc.com> wrote:
>
> Provide means, in the form of a `--with-toolexeclibdir=' configuration
> option, to override the default installation directory for target
> libraries, otherwise known as $toolexeclibdir. This is so that it is
> possible to get newly-built libraries, particularly the shared ones,
> installed in a common place, so that they can be readily used by the
> target system as their host libraries, possibly over NFS, without a need
> to manually copy them over from the currently hardcoded location they
> would otherwise be installed in.
>
> In the presence of the `--enable-version-specific-runtime-libs' option
> and for configurations building native GCC the option is ignored.
>
> ---
> On Mon, 20 Jan 2020, Ian Lance Taylor wrote:
>
> > > 2. push all the bits sans the libgo/ part and you'll push the libgo/ part
> > > to your repo and then you'll merge it to GCC.
> > >
> > > There is a slight technical advantage to going with #1 as there'll be no
> > > window where the new option is not consistently supported; it's also less
> > > work as you won't have to do the merge. But I have no strong preference
> > > either way.
> >
> > I'd rather do #2. Thanks. A small window is unlikely to matter to
> > anyone. Let me know when the rest of the patch is committed.
>
> This is the version I have committed. I've also attached the libgo part
> with a ChangeLog entry for your convenience (you'll have to write your own
> change description though).
Thanks. Committed upstream and to GCC master.
Ian
prev parent reply other threads:[~2020-01-24 14:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 14:26 [PATCH v3] " Maciej W. Rozycki
2020-01-21 0:44 ` Joseph Myers
2020-01-21 2:46 ` Maciej W. Rozycki
2020-01-21 5:07 ` Ian Lance Taylor
2020-01-24 11:27 ` [committed v4] " Maciej W. Rozycki
2020-01-24 14:36 ` Ian Lance Taylor [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='CAOyqgcXVUoc7E521w1bgP7=OxA9WABs=VzK_uNhp=2QggrOCfg@mail.gmail.com' \
--to=iant@golang.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gofrontend-dev@googlegroups.com \
--cc=joseph@codesourcery.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).