On Feb 17, 7:13 pm, gerhard <[EMAIL PROTECTED]> wrote:
Hi Gerhard,
> Thank you for the quick response!
> I used MKL for historical reasons
> unrelated to performance...
Ok, interesting to know.
> I think I will undefine CPPFLAGS and LDFLAGS
> to ensure the sage build process does not pick
> up my MKL installation.
Ok.
> That leaves my original question:
> since I need
> --with-recommended-packages=yes \
> --enable-R-shlib
> in the configure flags for R, is there an easier way
> than the sequence I use (as outlined in my first message)?
We will shortly offer an optional R.spkg with the recommended packages
enabled. If testing reveals that it doesn't break anywhere we will
then make that package standard. Since we removed the recommended
packages from our source tree it will take a little but of effort to
get that going, but it should happen for 2.10.3 or so. The R shlib
should be compiled since we use it for rpy - or am I getting this
wrong? Note that the R shlib is not installed in the default
SAGE_LOCAL/lib directory, but in $SAGE_LOCAL/lib/R/lib for some reason
I do not understand.
To answer your question: there is no automatic way to fix this unless
you use your script, but we should include a R.spkg more to your
liking shortly. We are tracking the issue at
http://trac.sagemath.org/sage_trac/ticket/2198
> Thanks,
> Gerhard
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
