From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin@cygwin.com
Cc: Achim Gratz <Stromeko@nexgo.de>
Subject: Re: Requesting ISL update
Date: Mon, 21 Sep 2015 09:54:00 -0000 [thread overview]
Message-ID: <55FFD3E7.4010008@dronecode.org.uk> (raw)
In-Reply-To: <87h9mpgrgw.fsf@Rainer.invalid>
On 20/09/2015 14:17, Achim Gratz wrote:
> JonY writes:
>> GCC prereq downloads 0.14, so that version it is.
>
> Done.
isl/libisl13 doesn't seem to have a setup.hint. Is that intended?
--
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:[~2015-09-21 9:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 10:04 JonY
2015-09-15 17:09 ` Michael Enright
2015-09-15 22:53 ` JonY
2015-09-19 6:35 ` Achim Gratz
2015-09-20 13:17 ` Achim Gratz
2015-09-20 13:46 ` JonY
2015-09-21 9:54 ` Jon TURNEY [this message]
2015-09-21 16:28 ` Achim Gratz
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=55FFD3E7.4010008@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=Stromeko@nexgo.de \
--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).