From: Dominik Vogt <vogt@linux.vnet.ibm.com>
To: libffi-discuss@sourceware.org
Subject: Re: [PATCH] Fix typo in help strings for --disable-(struct|raw_api)
Date: Mon, 24 Feb 2014 13:55:00 -0000 [thread overview]
Message-ID: <20140224135501.GA26585@linux.vnet.ibm.com> (raw)
In-Reply-To: <20140224134354.GA23591@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 211 bytes --]
And the regenerated fficonfig.h.in ...
-- snip --
2014-02-24 Dominik Vogt <dominik(dot)vogt(at)gmx(dot)de>
* fficonfig.h.in: Rebuilt
-- snip --
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt
IBM Germany
[-- Attachment #2: 0001-Rebuilt-fficonfig.h.in.patch --]
[-- Type: text/x-diff, Size: 904 bytes --]
From c2b7191020fb17bcbcc0293ab6f77132fdeafdb7 Mon Sep 17 00:00:00 2001
From: Dominik Vogt <vogt@de.ibm.com>
Date: Mon, 24 Feb 2014 14:51:24 +0100
Subject: [PATCH 1/2] Rebuilt fficonfig.h.in.
---
fficonfig.h.in | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fficonfig.h.in b/fficonfig.h.in
index f53b4bd..cac4b86 100644
--- a/fficonfig.h.in
+++ b/fficonfig.h.in
@@ -26,10 +26,10 @@
/* Cannot use malloc on this target, so, we revert to alternative means */
#undef FFI_MMAP_EXEC_WRIT
-/* Define this is you do not want support for the raw API. */
+/* Define this if you do not want support for the raw API. */
#undef FFI_NO_RAW_API
-/* Define this is you do not want support for aggregate types. */
+/* Define this if you do not want support for aggregate types. */
#undef FFI_NO_STRUCTS
/* Define to 1 if you have `alloca', as a function or macro. */
--
1.7.9.5
next prev parent reply other threads:[~2014-02-24 13:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 13:44 Dominik Vogt
2014-02-24 13:55 ` Dominik Vogt [this message]
2014-02-28 5:28 ` Anthony Green
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=20140224135501.GA26585@linux.vnet.ibm.com \
--to=vogt@linux.vnet.ibm.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).