From: Richard Henderson <rth@redhat.com>
To: libffi-discuss@sourceware.org
Subject: Re: [RFC] Proposal for m*vc build issue (#138)
Date: Wed, 12 Nov 2014 13:16:00 -0000 [thread overview]
Message-ID: <54635DAB.3080800@redhat.com> (raw)
In-Reply-To: <20141112130755.GA24721@linux.vnet.ibm.com>
On 11/12/2014 02:07 PM, Dominik Vogt wrote:
> I've attached a patch implementing option 4 from here:
> https://github.com/atgreen/libffi/issues/138 Please proof read the
> patch and let me know what you think. It might be good to
> specifically double check the detection of a compiler with complex
> support using macros.
Looks good to me.
r~
next prev parent reply other threads:[~2014-11-12 13:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 13:08 Dominik Vogt
2014-11-12 13:16 ` Richard Henderson [this message]
2014-11-12 13:26 ` Dominik Vogt
2014-11-12 13:36 ` Dominik Vogt
2014-11-12 13:46 ` Grégory Pakosz
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=54635DAB.3080800@redhat.com \
--to=rth@redhat.com \
--cc=libffi-discuss@sourceware.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).