From murdoch.duncan at gmail.com  Tue Jun 21 02:05:29 2016
From: murdoch.duncan at gmail.com (Duncan Murdoch)
Date: Mon, 20 Jun 2016 20:05:29 -0400
Subject: [Rd] xxx not available for .C in package yyy
In-Reply-To: <7E3AADC23AECB243A343EB0165E6DE6089BFAA8B@msgb06.nih.gov>
References: <7E3AADC23AECB243A343EB0165E6DE6089BFAA8B@msgb06.nih.gov>
Message-ID: <3f5a5e26-9cc4-497f-8acf-0ef0f34c16d8@gmail.com>

On 20/06/2016 5:47 PM, Izmirlian, Grant (NIH/NCI) [E] wrote:
> Hi R package developers. This is literally the strangest thing I've ever seen.
> Latest (as of a month ago) R under cygwin64.  I'm teaching an intern package
> building and using the .C interface.  The package compiles, but when it gets
> to "setting up lazy load" or some such it throws the error "triang" not available for .C()
> in package "randpkg".  Upon checking, after removing the current version of the package
> incrementing the package number just to make sure, commenting out the portion of the
> R code that calls .C(), then building, INSTALLING again, this time works. We are able
> to call .C("trian", ...) by hand inside of R, but then when we uncomment out the call
> in the .R file, it throws the error again. We've even retyped that portion of code, we've
> even dos2unix 'd everything.  Any thoughts?

We don't support Cygwin builds.

If you get this using one of our builds, put together a simple 
reproducible instance of it and make it available.  If it's only in 
Cygwin, you should do the same, and send it to someone there.

Duncan Murdoch



[Rd] xxx not available for .C in package yyy
Duncan Murdoch