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:
**
On Thu, 14 Jun 2007, Prof Brian Ripley wrote:
> You may prefer the version now in R-devel: this goes slightly the other
> way in that it loads all the Suggests/Enhances packages and also a dummy
> compatibility package for platform differences. Neither this nor the
> previous version can test the
Jeffrey Horner wrote:
> Duncan Murdoch wrote:
>> On 6/14/2007 10:49 AM, Jeffrey Horner wrote:
>>> Hi,
>>>
>>> Here's a patch to the readChar manual page (R-trunk as of today) that
>>> better clarifies readChar's return value.
>> Your update is not right. For example:
>>
>> x <- as.raw(32:96)
>>
Hi,
Strange things happen with missing args in S4 methods:
> setGeneric("mygen", signature="x", function(x, ...)
standardGeneric("mygen"))
[1] "mygen"
> setMethod("mygen", "character", function(x, y=12, z, ...) {cat(missing(y),
"\n"); cat(y, "\n")})
[1] "mygen"
> mygen("aa", z=99)
Duncan Murdoch wrote:
> On 6/14/2007 10:49 AM, Jeffrey Horner wrote:
>> Hi,
>>
>> Here's a patch to the readChar manual page (R-trunk as of today) that
>> better clarifies readChar's return value.
>
> Your update is not right. For example:
>
> x <- as.raw(32:96)
> readChar(x, nchars=rep(2,100)
On Mon, 11 Jun 2007, Seth Falcon wrote:
> Prof Brian Ripley <[EMAIL PROTECTED]> writes:
>
>> It seems that is happens if package tcltk is missing from the Depends:
>> list in the DESCRIPTION file. I just tested with Amelia and homals and
>> that solved the various warnings in both cases.
>
> Addi
On 6/14/2007 10:49 AM, Jeffrey Horner wrote:
> Hi,
>
> Here's a patch to the readChar manual page (R-trunk as of today) that
> better clarifies readChar's return value.
Your update is not right. For example:
x <- as.raw(32:96)
readChar(x, nchars=rep(2,100))
This returns a character vector of
Hi,
Here's a patch to the readChar manual page (R-trunk as of today) that
better clarifies readChar's return value. It could use some work as I'd
also like to add some text about using nchar() to find the length of the
string that readchar() returns, but I'm unsure which of type="bytes" or
typ
Please repost this on R-help,
which is appropriate here.
Regards, Martin Maechler
> "GK" == Gregory Kotler <[EMAIL PROTECTED]>
> on Wed, 13 Jun 2007 11:38:06 -0400 writes:
GK> Hi ALL,
GK> Do R have any tools for testing equality of coefficients of variation
GK> for k no
12 matches
Mail list logo
