From: "Maciej W. Rozycki" <macro@wdc.com>
To: Jeff Law <law@redhat.com>
Cc: gcc-patches@gcc.gnu.org, Mike Stump <mikestump@comcast.net>,
Chung-Lin Tang <cltang@codesourcery.com>,
Ian Lance Taylor <iant@golang.org>,
libffi-discuss@sourceware.org
Subject: Re: [PATCH v4 GCC 2/5] libffi/test: Fix compilation for build sysroot
Date: Mon, 6 Apr 2020 21:21:22 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.21.2004062107570.461@redsun52.ssa.fujisawa.hgst.com> (raw)
In-Reply-To: <884869974f813a01c4a6a9772b31366109a3b198.camel@redhat.com>
On Mon, 6 Apr 2020, Jeff Law wrote:
> > libffi/
> > * configure.ac: Add testsuite/local.exp to output files.
> > * configure: Regenerate.
> > * testsuite/local.exp.in: New file.
> > * testsuite/Makefile.am (EXTRA_DEJAGNU_SITE_CONFIG): New
> > variable.
> > * testsuite/Makefile.in: Regenerate.
> Oh, I see it now. THe patches I ack'd were actually for upstream libffi.
>
> You should actually wait for a libffi maintainer to ack those, not me :-) Sorry
> for the confusion.
Sorry to make it unclear. I chose to cc the other mailing list with the
libffi part of both submissions so as to give a chance to chime in to
members of both communities. We are quite tightly coupled with each other
here after all and my experience over the many years I have been involved
has been that the bits related to Autotools are often quite tricky and
hard to get right (Autotools are fine tools in my experience, it's just
you need to be thorough with them as they tend not to forgive a cursory
approach).
> Both backports are OK once they're upstreamed.
Thanks for your ack; it was my intent to get these upstream first, and I
realise there can be changes requested that will require the GCC backport
to be adjusted accordingly (and reviewed again).
Maciej
next prev parent reply other threads:[~2020-04-06 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.2.21.2004031338210.461@redsun52.ssa.fujisawa.hgst.com>
2020-04-03 23:01 ` Maciej W. Rozycki
2020-04-06 18:06 ` Jeff Law
2020-04-06 20:21 ` Maciej W. Rozycki [this message]
2020-04-03 23:01 ` [PATCH v4 GCC 3/5] libffi/test: Make `libffi-init' use $CC_FOR_TARGET Maciej W. Rozycki
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.LFD.2.21.2004062107570.461@redsun52.ssa.fujisawa.hgst.com \
--to=macro@wdc.com \
--cc=cltang@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@golang.org \
--cc=law@redhat.com \
--cc=libffi-discuss@sourceware.org \
--cc=mikestump@comcast.net \
/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).