Hi R-users,
talking about the compilation of rjags (gnu 4.4.7 - blas and lapack
routines) package in R I have solved the issue in the thread as follows:
Before compiling JAGS I need to recompile BLAS and LAPACK libraries with
-fPIC instruction:
BLAS Makefile:
[root@n14 library]# cat /home/
On 11/5/2015 9:45 AM, Rainer Hurling wrote:
Am 04.11.2015 um 21:36 schrieb Evan Cooch:
On 11/4/2015 2:08 PM, Evan Cooch wrote:
Greetings --
This has also been posted on the jags forum, but since I suspect the
problem is more 'R-related' than jags, will aos post here.
Decided to 'upgrade'
Am 05.11.2015 um 15:44 schrieb Evan Cooch:
> Well, sort of. I got sufficiently frustrated that I completely
> uninstalled R, jags, and everything related. Did a re-install using only
> versions of R nd JAGS found in the epel repo. No muss, no muss -- all
> works.
>
> Out of curiosity, uninstalled
Well, sort of. I got sufficiently frustrated that I completely
uninstalled R, jags, and everything related. Did a re-install using only
versions of R nd JAGS found in the epel repo. No muss, no muss -- all
works.
Out of curiosity, uninstalled again, and tried my usual sequence of
manually com
Am 04.11.2015 um 21:36 schrieb Evan Cooch:
On 11/4/2015 2:08 PM, Evan Cooch wrote:
Greetings --
This has also been posted on the jags forum, but since I suspect the
problem is more 'R-related' than jags, will aos post here.
Decided to 'upgrade' from jags 3.x.x to 4.x.x today, on my GNU/Linux
On 11/4/2015 3:31 PM, Yvan Richard wrote:
Hi Evan
The last version of rjags on CRAN is 4.4. Have you tried it?
http://cran.stat.auckland.ac.nz/web/packages/rjags/index.html
I did have the same problem before updating it, but it now works on my
Ubuntu with the new JAGS version.
Cheers,
-Yvan
On 11/4/2015 2:08 PM, Evan Cooch wrote:
Greetings --
This has also been posted on the jags forum, but since I suspect the
problem is more 'R-related' than jags, will aos post here.
Decided to 'upgrade' from jags 3.x.x to 4.x.x today, on my GNU/Linux
boxes (which run latest RHEL). Here are
I wonder if this is the problem -- on my system(s), R is installed to
/usr/lib64/R, whereas JAGS and associated files is in
/usr/local/lib/JAGS. I have a hunch that the problem relates to where
rjags expects to find things during install/compile, given how R was
compiled, and where it is insta
According to the README file in the rjags source code (in the tar.gz
file), you can apparently pass options to the configure script to
specify where JAGS is installed.
I'm confident you can solve your problem by following the instructions
in that README file.
On 5 November 2015 at 10:10, Evan Coo
Hi Evan
The last version of rjags on CRAN is 4.4. Have you tried it?
http://cran.stat.auckland.ac.nz/web/packages/rjags/index.html
I did have the same problem before updating it, but it now works on my
Ubuntu with the new JAGS version.
Cheers,
-Yvan
__
Am 04.11.2015 um 20:08 schrieb Evan Cooch:
> Greetings --
>
> This has also been posted on the jags forum, but since I suspect the
> problem is more 'R-related' than jags, will aos post here.
>
> Decided to 'upgrade' from jags 3.x.x to 4.x.x today, on my GNU/Linux
> boxes (which run latest RHEL).
Greetings --
This has also been posted on the jags forum, but since I suspect the
problem is more 'R-related' than jags, will aos post here.
Decided to 'upgrade' from jags 3.x.x to 4.x.x today, on my GNU/Linux
boxes (which run latest RHEL). Here are the basic details:
1\ used R 3.2.2 compil
12 matches
Mail list logo
