From: Csaba Raduly <rcsaba@gmail.com>
To: cygwin list <cygwin@cygwin.com>
Cc: Fergus <fergus@bonhard.uklinux.net>
Subject: Re: Needing the executable grap
Date: Mon, 14 Jan 2019 09:55:00 -0000 [thread overview]
Message-ID: <CAEhDDbDqcYN_9a4HzLT2SPhpiyQGkHr-cxw-4n_3XvjG5fY3bQ@mail.gmail.com> (raw)
In-Reply-To: <000001d4abca$83263610$8972a230$@bonhard.uklinux.net>
Hi Fergus,
On Mon, Jan 14, 2019 at 6:32 AM Fergus <fergus@bonhard.uklinux.net> wrote:
> Sadly the executable grap is not part of the Cygwin provision.
> I use a version derived from the same place as the current
> https://www.lunabase.org/~faber/Vault/software/grap/grap-1.45.tar.gz
> but actually it is v.1.42 from Goodness knows when and compiled under
> CYGWIN_NT-6.1 1.5.25(0.156/4/2).
> It works just fine under W7 and W10 and in the past under XP. It compiled,
> then, perfectly easily.
> I still have grap-1.42.tar.gz and can get the current grap-1.45.tar.gz from
> the location above.
> But I am unable to compile either under the current Cygwin.x86 or under
> Cygwin.x86_64.
>
What did you try and what was the error message?
Csaba
--
You can get very substantial performance improvements
by not doing the right thing. - Scott Meyers, An Effective C++11/14 Sampler
So if you're looking for a completely portable, 100% standards-conformat way
to get the wrong information: this is what you want. - Scott Meyers
(C++TDaWYK)
--
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:[~2019-01-14 9:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 5:32 Fergus
2019-01-14 9:55 ` Csaba Raduly [this message]
2019-01-14 15:05 ` Fergus
2019-01-14 15:08 ` Marco Atzeri
2019-01-14 19:12 ` Achim Gratz
2019-01-14 13:10 ` Corinna Vinschen
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=CAEhDDbDqcYN_9a4HzLT2SPhpiyQGkHr-cxw-4n_3XvjG5fY3bQ@mail.gmail.com \
--to=rcsaba@gmail.com \
--cc=cygwin@cygwin.com \
--cc=fergus@bonhard.uklinux.net \
/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).