Jason Roberts wrote:
> Hi Laurent,
>
>> The libR is used as a shared library.
>> Under win32, and AFAIUI, that should translate as using an unbound DLL
>> (otherwise the same version of libR will be required) and hold as long
>> as the names used from the symbol table presented by libR.so do not
On 20 March 2009 at 18:45, Agustin Lobo wrote:
| Hi!
|
| I'm installing rpy2 on a machine with ubuntu 8.04, having both R-base
| and R-base-dev
|
| When I run
| python setup.py install
| I get
| /usr/bin/ld: cannot find -lRlapack
| collect2: ld returned 1 exit status
| error: command 'gcc' fa
Hi!
I'm installing rpy2 on a machine with ubuntu 8.04, having both R-base
and R-base-dev
When I run
python setup.py install
I get
/usr/bin/ld: cannot find -lRlapack
collect2: ld returned 1 exit status
error: command 'gcc' failed with exit status 1
I do have lapack.so in
in /usr/lib/R/modules
Hi Laurent,
> The libR is used as a shared library.
> Under win32, and AFAIUI, that should translate as using an unbound DLL
> (otherwise the same version of libR will be required) and hold as long
> as the names used from the symbol table presented by libR.so do not
change.
> In the case it doe
Laurent,
Thank you very much for the reply.
> I am not certain of which way the risk probability stand (compile each
> time, or compile once and hope for the best). Time will tell.
So rpy2 does not require recompilation every time R is released? How is it
binding to R then? (I have not looked at
Jason Roberts wrote:
> Laurent,
>
> Thank you very much for the reply.
>
>> I am not certain of which way the risk probability stand (compile each
>> time, or compile once and hope for the best). Time will tell.
>
> So rpy2 does not require recompilation every time R is released? How is it
> bin
