#9668: Fix hardcoding of paths in R binary
---------------------------------------------------------------------------------------------------------------+
Reporter: kcrisman
| Owner: leif
Type: defect
| Status: needs_review
Priority: major
| Milestone: sage-5.4
Component: packages
| Resolution:
Keywords: R spkg R.sh.in libR.pc pkg-config hard-coded package
installation R_HOME_DIR sd32 r-project | Work issues:
Report Upstream: N/A
| Reviewers:
Authors: John Palmieri
| Merged in:
Dependencies: #9906
| Stopgaps:
---------------------------------------------------------------------------------------------------------------+
Comment (by jhpalmieri):
Replying to [comment:9 leif]:
> * Address / check the following (copied from
[comment:ticket:10967:14]):
> {{{
> The problem was with hard-coded paths, not the
> permissions. Anyway, the fix was easy. I opened all the files listed
> above by George:
> sage/local/lib/R/bin/R
> sage/local/lib/R/bin/libtool
> sage/local/lib/R/etc/Makeconf
> sage/local/lib/R/etc/ldpath
> sage/local/lib/R/etc/Renviron
> sage/local/bin/R
> and edited obvious lines containing hardcoded paths (using find-
> replace-all at once).
> }}}
It's easy enough to add these to the "for" loop that I added to spkg-
install, so I might as well do that. For what it's worth, the binary files
`Rscript` in both local/bin and local/lib/R/bin also have the path hard-
coded in them, but I don't know how to fix this, or whether it's
important. When are those files used?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9668#comment:19>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
