From: Florian Weimer <fw@deneb.enyo.de>
To: Jeff Law via Libffi-discuss <libffi-discuss@sourceware.org>
Cc: "Maciej W. Rozycki" <macro@wdc.com>,
law@redhat.com, Mike Stump <mikestump@comcast.net>,
gcc-patches@gcc.gnu.org, Ian Lance Taylor <iant@golang.org>,
Chung-Lin Tang <cltang@codesourcery.com>
Subject: Re: [PATCH v5 GCC] libffi/test: Fix compilation for build sysroot
Date: Wed, 29 Apr 2020 22:48:24 +0200 [thread overview]
Message-ID: <87a72uggrr.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <10b639b335a1f9a064a40410f79fe4c0ba9b749e.camel@redhat.com> (Jeff Law via Libffi-discuss's message of "Wed, 29 Apr 2020 11:14:35 -0600")
* Jeff Law via Libffi-discuss:
> FWIW, I'm expecting Florian to be digging into some libffi stuff
> relatively soon and once those issues are ironed out, there'll be a
> push for a libffi upstream release -- which seems like a good place
> to re-sync GCC to the upstream libffi master.
I'm not going to work on the master branch for now, so this should not
impact the release. The goal is specifically to support more hardware
for legacy binaries with the old libffi.so.6 soname.
next prev parent reply other threads:[~2020-04-29 20:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 13:18 Maciej W. Rozycki
2020-04-22 18:04 ` Jeff Law
2020-04-25 20:33 ` Maciej W. Rozycki
2020-04-29 17:14 ` Jeff Law
2020-04-29 20:48 ` Florian Weimer [this message]
2023-09-12 10:58 ` libffi: Consider '--with-build-sysroot=[...]' for target libraries' build-tree testing (instead of build-time 'CC' etc.) [PR109951] (was: [PATCH v5 GCC] libffi/test: Fix compilation for build sysroot) Thomas Schwinge
2023-10-25 8:30 ` [PING] " Thomas Schwinge
2023-10-26 13:32 ` [PING] libffi: Consider '--with-build-sysroot=[...]' for target libraries' build-tree testing (instead of build-time 'CC' etc.) [PR109951] Jeff Law
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=87a72uggrr.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=cltang@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@golang.org \
--cc=law@redhat.com \
--cc=libffi-discuss@sourceware.org \
--cc=macro@wdc.com \
--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).