Bug 246943

Summary:	R backend: when compiling, R should be run with --no-init-file
Product:	[Applications] cantor	Reporter:	Ryan Thompson <rct+bugs>
Component:	r-backend	Assignee:	Alexander Rieder <alexanderrieder>
Status:	RESOLVED FIXED
Severity:	normal	CC:	alexanderrieder, filipe, warquark
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:	14.11.80
Sentry Crash Report:

Description Ryan Thompson 2010-08-06 22:43:54 UTC

Version:           unspecified (using Devel) 
OS:                Linux

I had a broken ~/.Rprofile while trying to build cantor's R backend, and this broke the build process because it runs R without specifying --no-init-file. To fix this, I added this option to every invocation of R in src/backends/R/rserver/CMakeLists.txt.

If building the R backend will never require the user's init file, I suggest not loading it, as it could cause problems. Ditto for --no-site-file.



Reproducible: Always

Steps to Reproduce:
1. Create a ~/.Rprofile that raises an error.
2. Try to build cantor's R backend. When it gets to the part where it needs to run R, it will fail and abort.

Comment 1 Ryan Thompson 2010-09-02 20:34:45 UTC

Actually, it might be even better to run with --vanilla. That won't load any user- or site-specific init files at all.

Comment 2 Ryan Thompson 2010-09-02 20:39:20 UTC

If you want to add '-vanilla' automatically to all invocations of R within the kdeedu tree, I've done it with the following one-liner, run in the main kdeedu directory:

ack -ai '\$\{R_EXECUTABLE\}' -l | xargs -n1 perl -lape 's/\$\{R_EXECUTABLE\}/$& --vanilla/' -i

You'll need ack (http://betterthangrep.com/) installed. You can use grep for the same thing if you figure out the options.

Comment 3 Nikita Sirgienko 2018-05-08 19:56:23 UTC

I Close this outdated bug, because as I see, this solved after v14.11.80, if I am not mistake.