From: Ian Lance Taylor <iant@golang.org>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: David Edelsohn <dje.gcc@gmail.com>,
Jakub Jelinek <jakub@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v2 0/4] libffi: Sync with upstream
Date: Sat, 16 Oct 2021 12:21:33 -0700 [thread overview]
Message-ID: <CAKOQZ8ysn7sV9=0y6cqW5EcHz1JGAS=2uy-rPeiUtdhyAfVBzA@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOpp_=TLGm7Rg_jXWrFo372O8SHZhGhqrWZiUjjhSsPEZg@mail.gmail.com>
On Sat, Oct 16, 2021 at 10:14 AM H.J. Lu via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> Go on master branch isn't buildable on AIX. What should I do
> next to get my libffi sync patches into master branch?
Is the only problem you are having the missing-objcopy problem? To
fix that one, install the GNU binutils.
There are people who regularly use gccgo on AIX and send fixes for it,
I don't think it could be very badly broken.
Ian
next prev parent reply other threads:[~2021-10-16 19:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 15:50 H.J. Lu
2021-09-02 15:50 ` [PATCH v2 1/4] libffi: Add HOWTO_MERGE, autogen.sh and merge.sh H.J. Lu
2021-09-02 15:50 ` [PATCH v2 2/4] libffi: Sync with libffi 3.4.2 H.J. Lu
2021-09-02 15:50 ` [PATCH v2 3/4] libffi: Integrate build with GCC H.J. Lu
2021-09-02 15:50 ` [PATCH v2 4/4] libffi: Integrate testsuite with GCC testsuite H.J. Lu
2021-10-10 13:55 ` PING^1 [PATCH v2 0/4] libffi: Sync with upstream H.J. Lu
2021-10-13 12:45 ` Richard Biener
2021-10-13 12:56 ` H.J. Lu
2021-10-13 13:03 ` Richard Biener
2021-10-13 13:42 ` H.J. Lu
2021-10-16 0:06 ` H.J. Lu
2021-10-16 0:22 ` David Edelsohn
2021-10-16 11:48 ` H.J. Lu
2021-10-16 17:04 ` David Edelsohn
2021-10-16 17:13 ` H.J. Lu
2021-10-16 19:21 ` Ian Lance Taylor [this message]
2021-10-16 19:53 ` David Edelsohn
2021-10-16 19:58 ` H.J. Lu
2021-10-16 20:07 ` David Edelsohn
2021-10-17 13:26 ` H.J. Lu
2021-10-18 15:04 ` David Edelsohn
2021-10-18 15:08 ` H.J. Lu
2021-10-19 15:02 ` David Edelsohn
2021-10-19 18:01 ` H.J. Lu
2021-10-24 20:36 ` Iain Sandoe
2021-10-24 20:40 ` H.J. Lu
2021-10-25 6:58 ` Iain Sandoe
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='CAKOQZ8ysn7sV9=0y6cqW5EcHz1JGAS=2uy-rPeiUtdhyAfVBzA@mail.gmail.com' \
--to=iant@golang.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=jakub@redhat.com \
/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).