similar to: .Fortran successful, R locks up.

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

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, Please forgive me if this is a stupid question, but I have searched the lists and can not find an answer for something that should be pretty simple. I am loooking to perform a net file close on a samba shared file that is open from a windows machine. I can not get it to work in on my mac, or from a bsd based clustered file system. The closest I can get to it is performing an smbstatus

CRAN (and crantastic) updates this week New packages ------------ * bisectr (0.0.2) Maintainer: Winston Chang Author(s): Winston Chang <winston at stdout.org> License: GPL-2 http://crantastic.org/packages/bisectr Tools to find bad commits with git bisect * CUMP (1.0) Maintainer: Xuan Liu Author(s): Xuan Liu <liuxuan at bu.edu> and Qiong Yang <qyang at bu.edu>

Hi Stepan, Sorry for the delay. It's great that you are working on MergeFunctions as well and I agree, we should definitely try to combine our efforts to improve MergeFunctions. Just to give you some context, the pass (with the similar function merging patch) is already being used in a production setting. From my point of view, it would be better if we focus on improving its capability

Hello Sean and Tobias, Sean, Thank you. Could you describe Nick's ideas in few words or give me links to your discussion, so I could adapt my ideas to it. Tobias, Your patch fails on several modules in my benchmark (73 of ~1800 tests). I have sent one as attachment. See statistics files for more details, all the .ll files you could simply find in test-suite object directory (after