#20655: R installation failing on Cygwin
------------------------------------+------------------------
       Reporter:  embray            |        Owner:
           Type:  defect            |       Status:  new
       Priority:  major             |    Milestone:  sage-7.3
      Component:  porting: Cygwin   |   Resolution:
       Keywords:  windows cygwin R  |    Merged in:
        Authors:                    |    Reviewers:
Report Upstream:  N/A               |  Work issues:
         Branch:                    |       Commit:
   Dependencies:                    |     Stopgaps:
------------------------------------+------------------------

Comment (by embray):

 Okay, I think this is a bug in R IMO.

 R installs a bunch of "scripts" particular to R with names like `BUILD`
 and `INSTALL`.  R's install mistakenly marks these "scripts" as executable
 even though they do not contain a shebang line, so they are technically
 not executable in that sense.  Instead it runs those scripts from a main
 script (called `Rcmd`) using `exec`.

 The problem here is that `Rcmd` only run these R-specific scripts ''if''
 they are executable, and exist in `$R_HOME/bin`.  Realistically just
 whether they exist and are files in `$R_HOME/bin` should be good enough,
 since there shouldn't be any non-executable files in there.   If nothing
 else it should try to exec and if that fails it will return a permission
 error.  On Cygwin `exec` doesn't care if the file is marked executable or
 not, for this reason.  It will just try to execute it.

--
Ticket URL: <http://trac.sagemath.org/ticket/20655#comment:2>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to