hi, Duncan,
thanks for the reply, and the pointer to the XML package.
> I don't understand why configure needs access to DESCRIPTION.in. What
> is it reading there?
actually, ./configure is setting the version number in DESCRIPTION,
using DESCRIPTION.in as a template. in configure.ac, i have:
-
On 04/07/2014 3:27 PM, Greg Minshall wrote:
hi. i'm building a package using autotools. to propagate the package
version number from configure.ac to DESCRIPTION, i'm using a
DESCRIPTION.in file. both of these files are "shar"'d below.
i need to distribute the DESCRIPTION.in file, as ./configu
hi. i'm building a package using autotools. to propagate the package
version number from configure.ac to DESCRIPTION, i'm using a
DESCRIPTION.in file. both of these files are "shar"'d below.
i need to distribute the DESCRIPTION.in file, as ./configure will need
it. but, "R CMD check" wants to
On 04/07/2014 9:47 AM, Dalthorp, Daniel wrote:
Thank-you for the prompt and helpful response. It sounds like all I
need is a very simple fix, but it eludes me.
I am trying to call a custom C function from R to speed a calculation.
I'm on Windows 7 with R 3.0.2 and the latest Rtools. I run R CM
later I tried plain-vanilla, well.. redhats' and derivatives
default packages and they all fail:
> ## PR#4582 %*% with NAs
> stopifnot(is.na(NA %*% 0), is.na(0 %*% NA))
> ## depended on the BLAS in use.
>
>
> ## found from fallback test in slam 0.1-15
> ## most likely indicates an inaedquate BLA
On 03/07/2014, 7:53 PM, Dalthorp, Daniel wrote:> I've seen that many
people have had trouble using Rtools for a 64-bit
> compile of C functions. For some, a quick change in path statement
seems to
> corrects the problem; for others, apparently not. For me? I've been
working
> at path statements and
