Skip to content

[Bioc-devel] R CMD SHLIB throwing error on zin1 (linux) BioC nightly build

3 messages · Dan Tenenbaum, Martin Morgan, Obenchain, Valerie

#
----- Original Message -----
Probably both. We made a change, removing R from the PATH on the linux and windows machines (on Mac R is in /usr/bin so it's a bad idea to remove that directory from the PATH) because we realized that there are packages that fail when R is not in the PATH, and one can't assume that R will always be in the path, so we wanted to make sure those packages failed so that we'd find the problems. That seems to be what is happening in your case.

I'm not sure what the exact syntax is, but your makefile should reference R as $R_HOME/bin/R.

Dan
#
At least for the R package side of things, I think the question of how to invoke R CMD in a Makefile is moot for AnalysisPageServer -- remove the Makefile, and the shared object is created automatically when the package is built with R CMD build AnalysisPageServer.

But for the record the format for referring to R in Writing R Extensions in a Makefile is

    "${R_HOME}/bin/R" ...

${R_HOME} is an environment variable, quotes allow for spaces in the path. A more cross-platform version is  I think

    "${R_HOME}/bin${R_ARCH_BIN}/R"

where on single-architecture platforms ${R_ARCH_BIN} is undefined hence harmless.

Somewhat circularly, R_HOME is set by R CMD

$ env|grep R_HOME
$ R CMD env|grep R_HOME
R_HOME=/home/mtmorgan/bin/R-devel
$ Rrel CMD env|grep R_HOME
R_HOME=/home/mtmorgan/bin/R-3-2-branch
2 days later
#
Hi Brad,

Following up on this because AnalysisPageServer is still broken in
release. Can you please fix?

Thanks.
Valerie
On 12/14/2015 01:36 PM, Morgan, Martin wrote:
This email message may contain legally privileged and/or confidential information.  If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited.  If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you.