From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin R usability
Date: Mon, 17 Aug 2015 14:12:00 -0000 [thread overview]
Message-ID: <55D1EBD8.8000607@gmail.com> (raw)
In-Reply-To: <tencent_12266CBA39850A13141D72C3@qq.com>
On 17/08/2015 15:41, foehn wrote:
> Hi there,
>
> I read that there were issues (mainly with the BLAS library) in the Cygwin port of R (http://r.789695.n4.nabble.com/cygwin-R-2-14-0-build-fail-td4035136.html). And till today the official R site has not been supportive of the Cygwin version of R (https://cran.r-project.org/doc/manuals/r-release/R-admin.html#Cygwin), while there are number of people using this "unofficial" port regardless of the caveats showed in the official R site (http://stackoverflow.com/search?q=R+cygwin). A thread on Stack Overflow was posted asking about this "chaos" (http://stackoverflow.com/questions/31962159/cygwin-r-usability) but nobody seemed to be able to address it fully as they are not Cygwin developers. Therefore I send this mail to the insiders and ask specifically for the current situation of the Cygwin port of R:
>
R developers have a peculiar view on Cygwin. For them what is not build
by them is unsupported. In this view almost all cygwin software is
unsupported.
> -) Has the BLAS issue been addressed in the current Cygwin port of R?
Cygwin build use the integrated R BLAS patched, not Lapack one.
So handling of NaN is as expected by R.
> -) Beside the BLAS issue, is there any additional problem? Can it pass the building test?
It pass most of tests. There are some failures on IO formatting, but I
never investigated the root cause.
> -) In short, is current Cygwin port of R (v3.1.3, 64-bit) usable in serious sense?
I expect so.
If you find any serious issue, let me know.
>
> Thanks to the efforts for porting R to Cygwin and more thanks in advance to anybody responding to this mail,
> Foehn
Regards
Marco
--
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
prev parent reply other threads:[~2015-08-17 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 13:41 foehn
2015-08-17 14:12 ` Marco Atzeri [this message]
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=55D1EBD8.8000607@gmail.com \
--to=marco.atzeri@gmail.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).