Michael,

On Apr 23, 4:23 pm, mabshoff <[EMAIL PROTECTED]
dortmund.de> wrote:
> Hi Steve,
>
> we are now tracking the issue at #3011.
>
> On Apr 23, 10:08 pm, strogdon <[EMAIL PROTECTED]> wrote:
>
>

--- CUT ---

>
>
> > I've built sage previously, but without R installed. I suspect the
> > installed (Portage) R is conflicting with what sage does. Let me know
> > if you wish to see the install.log. I'm presently re-building sage in
> > a shell where I've disabled the R_HOME variable.
>
> Good. Let me know what that works. R itself is rather brittle and uses
> hard coded locations in a bunch of shell files. I mean to patch that
> out of the files and upgrading to R 2.6.2 or 2.7 [once it is out] will
> be a good occasion to clean that up.
>

Everything built in a shell where R_HOME was disabled and the test

     ./sage -t  devel/sage/sage/stats/test.py

passed in that shell. The test failed in a shell where the R_HOME
variable was set with the same failure as noted above.

>
> Cheers,
>
> Michael

Steve
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to