From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps <cygwin-apps@cygwin.com>
Subject: Patch for graphite2 1.3.11
Date: Mon, 19 Mar 2018 12:36:00 -0000 [thread overview]
Message-ID: <7ad93e85-e9c8-c135-9f74-aa39a032f166@cornell.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 203 bytes --]
Yaakov,
FYI, I had occasion to build graphite2-1.3.11 in connection with TeX
Live, and I needed the attached patch. I've reported this upstream:
https://github.com/silnrsi/graphite/issues/32
Ken
[-- Attachment #2: 0001-Don-t-include-intsafe.h-on-Cygwin.patch --]
[-- Type: text/plain, Size: 754 bytes --]
From 474d863fa779e5ae5568e90d7cec8928878229de Mon Sep 17 00:00:00 2001
From: Ken Brown <kbrown@cornell.edu>
Date: Sun, 18 Mar 2018 11:25:09 -0400
Subject: [PATCH] Don't include intsafe.h on Cygwin
This is a w32api header, which brings in several other such headers
and breaks the build.
---
src/inc/Main.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/inc/Main.h b/src/inc/Main.h
index f66b48d..2c64c6b 100644
--- a/src/inc/Main.h
+++ b/src/inc/Main.h
@@ -86,7 +86,7 @@ struct telemetry {};
#define HAVE_BUILTIN_OVERFLOW
#endif
#if defined(__has_include)
- #if __has_include(<intsafe.h>)
+ #if __has_include(<intsafe.h>) && !defined(__CYGWIN__)
#define HAVE_INTSAFE_H
#endif
#elif defined(_WIN32)
--
2.16.2
reply other threads:[~2018-03-19 12:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=7ad93e85-e9c8-c135-9f74-aa39a032f166@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@cygwin.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).