search for: drf28

...Hydrology") > .Fortran("junk") SWAT2005 Soil & Water Assessment Tool PC Version Program reading from file.cio . . . executing list() > ^C > q("n") ^C > obejcts() ^C > q() ^C > ^Z [1]+ Stopped r DRF28:~/cornell/ecohydrology/swat_example/SJ_R_test_mac/Scenarios/Default/TxtInOut_R dan$ killall R [1]+ Terminated r Output from top during lockup: PID COMMAND %CPU TIME #TH #PRTS #MREGS RPRVT RSHRD RSIZE VSIZE 40750 R 96.6% 1:56.07 1 17 87 15M 1384K-...

Dear mac folks, I have started porting a large legacy toolset maintained in windows and heavily mpi laden so it can be used across platforms in R... so I am building a package out of it. On this note, I am noticing that almost all of the mpi dependent packages do not compile on the CRAN repositories.... with the basic issue that it appears it can not find mpi installed: configure: error:

Howdy, I was under the impression that CRAN took care of automagically making sure the CRAN compiled fortran was linked to the fortran libs distributed in R binaries. Today was the first day I was on a mac without Xcode and found my fortran based package has issues, which appears only on the mac. Do we need to have a special compile library path set in the Makefile to direct CRAN to the R

Sorry for this intrusion, but I am confused by two statements that appear to conflict at some level in Writing R Extensions, and wanted to make sure I understand the answer to: Can we distribute a portable executable compiled from source by CRAN in CRAN? The following section of Writing R Extensions appears to not be addressing this issue, as in this case we are discussing portable CRAN compiled