From: Fergus Daly <fergusd84@outlook.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Cc: Fergus Daly <fergusd84@outlook.com>
Subject: RE: grap, anybody?
Date: Tue, 07 Jan 2020 22:10:00 -0000 [thread overview]
Message-ID: <LNXP265MB143684B025EAFDE83FEF783AA43F0@LNXP265MB1436.GBRP265.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <LNXP265MB14369F26E5EABFAFB4EAD90CA43F0@LNXP265MB1436.GBRP265.PROD.OUTLOOK.COM>
>> Try following patch.
--- configure.ac.orig 2014-08-31 00:33:45.000000000 +0900
+++ configure.ac 2020-01-07 08:43:59.559103700 +0900
@@ -45,10 +45,10 @@
AC_MSG_CHECKING(if ${CXX} supports -std=c++0x)
old_cxxflags="$CXXFLAGS"
old_cppflags="$CPPFLAGS"
-CXXFLAGS="$CXXFLAGS -std=c++0x"
-CPPFLAGS="$CPPFLAGS -std=c++0x"
+CXXFLAGS="$CXXFLAGS -D_XOPEN_SOURCE=700"
+CPPFLAGS="$CPPFLAGS -D_XOPEN_SOURCE=700"
AC_TRY_COMPILE([], [], [
- CX0FLAGS="-std=c++0x"
+ CX0FLAGS=""
AC_MSG_RESULT(yes)
], [
CX0FLAGS=""
> Thank you! This patch enabled compilation of the grap-1.45 executable for 32-bit and 64-bit Cygwin respectively.
I'm just not up to it, but given the trivial nature of the single required patch, is there anybody out there who could take this on for the Cygwin provision?
(There must be 00s of users who need it? I'm truly surprised that grap, or rather its lack, hasn't had a much higher historical profile in this forum.)
Does it matter that the source files https://www.lunabase.org/~faber/Vault/software/grap/grap-1.45.tar.gz are "owned" by somebody else?
(I imagine it does. Just asking.)
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2020-01-07 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 17:36 Fergus Daly
2020-01-07 22:10 ` Fergus Daly [this message]
2020-01-07 22:41 ` Marco Atzeri
-- strict thread matches above, loose matches on Subject: below --
2020-01-06 21:40 bonhard
2020-01-07 6:17 ` Brian Inglis
2020-01-07 11:28 ` Takashi Yano
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=LNXP265MB143684B025EAFDE83FEF783AA43F0@LNXP265MB1436.GBRP265.PROD.OUTLOOK.COM \
--to=fergusd84@outlook.com \
--cc=cygwin@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).