R does not work inside sage if LD_LIBRARY_PATH includes /sw/lib.   
(Which it ordinarily wouldn't, that was a mistake of mine.)  That bug  
is pretty trivial and easily fixed.

But I found that R is the only component of sage that links to system  
frameworks.  (Aside from python.)  That seems to be a bit inconsistent  
for sage, i.e. R obviously does not link to Apple frameworks on other  
platforms.

The aqua device is compiled in Mac-sage-R, though my feeling is that  
it wouldn't be a drama to remove it.  There is plenty inside the R  
configure script about detecting CoreFoundation, though no simple  
option.  I think it would be a good idea to switch off CF as well as  
Aqua.

So the two questions are:
* would switching off Aqua have any benefit, or inconvenience anyone?
* would switching off CF be a good idea too?

D

=== BACKGROUND ===
r.eval('1+1') fails

The fail message includes the following:
before (last 100 chars): ions/A/Frameworks/ImageIO.framework/Versions/ 
A/ImageIO
   Expected in: /sw/lib/libJPEG.dylib

sage -t r.devel/sage-main/sage/interfaces/py fails, or fails to complete
sage -testall only gave problems with R, suggesting the fault lies  
there.


=== FIXES ===
All of these work:
* Renaming /sw so that the offending library can't be found.
* Removing /sw/lib from LD_LIBRARY_PATH
* Setting OSXFW="--enable-R-framework=no --with-aqua=no" inside R spkg- 
install




==================================
David J Philp
Postdoctoral Fellow
National Centre for Epidemiology and Population Health
Building 62, cnr Mills Rd & Eggleston Rd
The Australian National University
Canberra ACT 0200 Australia

T: +61 2 6125 8260
F: +61 2 6125 0740
M: 0423 535 397
W: http://nceph.anu.edu.au/

CRICOS Provider #00120C





--~--~---------~--~----~------------~-------~--~----~
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