On Fri, 15 Jun 2007, [EMAIL PROTECTED] wrote:
> Prof. Ripley,
>
> I had a feeling I was going a little too deep into the R source code
> in order to pull out these functions. I particularly like these La_*
> functions calling the LAPACK routines, because they have so much of
> the error checking
Prof. Ripley,
I had a feeling I was going a little too deep into the R source code
in order to pull out these functions. I particularly like these La_*
functions calling the LAPACK routines, because they have so much of
the error checking already built-in. I can just copy the code over,
and hope
He wants "La_dgesv", which is not an LAPACK entry point at all, but a
private part of R. The header it is in is private and not installed.
There is no guarantee that it will remain visible to an R package, and the
only safe thing to do is to copy the code.
On Thu, 14 Jun 2007, [EMAIL PROTECTED
On Thu, Jun 14, 2007 at 11:27:44PM +0100, Hin-Tak Leung wrote:
> Try this? (this is on 2.5.0, I don't use 2.4.x anymore)
>
> #include
>
I tried this, but I still get the warning of implicit declaration of
function. It does compile though.
> Have you actually tried grep dgesv $R_HOME/include/*
Try this? (this is on 2.5.0, I don't use 2.4.x anymore)
#include
Have you actually tried grep dgesv $R_HOME/include/* $R_HOME/include/*/*
to see which file to include for dgesv ??
HTL
[EMAIL PROTECTED] wrote:
> Hey Everyone,
>
> I'm running R 2.4.0 on Debian etch 4.0, and I'm trying to call s
Hey Everyone,
I'm running R 2.4.0 on Debian etch 4.0, and I'm trying to call some
LAPACK functions from the C code in my package. Actually, to be
honest I'm not really having trouble using commands such as La_dgesv
from within my C code, but I do get warning when compiling the package
saying:
**
