hi guys,
I'd like to ask, and I believe this place here should be best as who can
know better, if building R with different compilers and opt flags is
something worth investing time into?
Or maybe this a subject that somebody has already investigated. If yes
what then are the conclusion?
Reason
On 13/06/2019 16:14, Dirk Eddelbuettel wrote:
> On 13 June 2019 at 16:05, lejeczek via R-devel wrote:
> | I'd like to ask, and I believe this place here should be best as who can
> | know better, if building R with different compilers and opt flags is
> | something worth in
Hi guys,
I want to ask devel for who knows better - having multiple
nodes serving users home dirs off the same shared network
filesystem : are there any precautions or must-dos &
must-donts in order to assure healthy and efficient parallel
Rs running simultaneously - and I don't mean obvious stuff
dear devel,
I thought you guys would know best - I have an R which fails to get
communicate outside via a proxy, and Squid's logs show:
...
1581432434.501 0 10.5.8.17 TAG_NONE/400 4064 %C5/%B6* -
HIER_NONE/- text/html
1581432497.231 0 10.5.8.17 TAG_NONE/400 4570 NONE
error:invalid-req
On 11/02/2020 14:54, lejeczek via R-devel wrote:
> dear devel,
>
> I thought you guys would know best - I have an R which fails to get
> communicate outside via a proxy, and Squid's logs show:
>
> ...
>
> 1581432434.501 0 10.5.8.17 TAG_NONE/400 4064 %C5/%
I'm not sure if I should bother you team with this,
apologies in case it's a bother.
I'm trying gcc 6.2.1 (from devtoolset-6) with R, everything
seems to work just fine, except for mzR.
Here is failed build:
g++ -m64 -shared -L/usr/lib64/R/lib -Wl,-z,relro -o mzR.so
cramp.o ramp_base64.o ram
ced in an
earlier compilation step; they likely failed in some way,
so you need to provide the complete compilation output.
Did you do this on a version of the package that did not
have any previous build artifacts (e.g., via biocLite() or
from a fresh svn checkout)?
Martin
On 12/21/2016 12:00
