Re: [Rd] Problem with dyn.load() under Windows 64bit at CRAN

2010-06-30 Thread Uwe Ligges
Dominick, your messages are all in my Inbox, I just have not yet found the time to look in more detail. On 30.06.2010 15:44, Dominick Samperi wrote: The package cxxPack builds without problems at CRAN under all OS's except Windows 64bit, and in the case of Windows 64bit there is a problem in

Re: [Rd] Tips for debugging: R CMD check examples

2010-06-30 Thread hadley wickham
> How did you 'run' it?   I suspect you source()d it, not at all the same > thing.  I have yet to encounter a problem which > > R --vanilla < foo-Ex.R > > or perhaps > > env LANGUAGE=en R --vanilla --encoding=latin1 < foo-Ex.R > > did not reproduce. Thanks, that was exactly what I was looking for.

Re: [Rd] Tips for debugging: R CMD check examples

2010-06-30 Thread Prof Brian Ripley
On Wed, 30 Jun 2010, hadley wickham wrote: R CMD check produces a foo-Ex.R file where foo is the package name. You could start by sourcing that file in R --vanilla and see where it fails and also use standard debugging tools in R from there (i.e. drop into a debugger on error). I knew about th

[Rd] Problem with dyn.load() under Windows 64bit at CRAN

2010-06-30 Thread Dominick Samperi
The package cxxPack builds without problems at CRAN under all OS's except Windows 64bit, and in the case of Windows 64bit there is a problem in a call to dyn.load(). This call happens while processing the package vignette, and the odd thing about this is that there are several calls to dyn.load() t

Re: [Rd] Tips for debugging: R CMD check examples

2010-06-30 Thread Hadley Wickham
> Not a real tip, but when it occurs I immediately > check for namespace issues (which often turn out > to be the origin). Things I do are I agree that namespace issues are often a problem, and are never easy to diagnose - I often find that I've forgotten to export a method definition so other cod

Re: [Rd] Tips for debugging: R CMD check examples

2010-06-30 Thread hadley wickham
> R CMD check produces a foo-Ex.R file where foo is the package name. You > could start by sourcing that file in R --vanilla and see where it fails > and also use standard debugging tools in R from there (i.e. drop into a > debugger on error). I knew about the foo-Ex.R file, but unfortunately runn

Re: [Rd] Tips for debugging: R CMD check examples

2010-06-30 Thread Spencer Graves
Hi, Hadley: 1. Is your memory clear when you run the examples successfully? I.e., start with "rm(list=objects())", then try the examples that work interactively but fail in "R CMD check". 2. Also, does "R CMD check" give any warnings, e.g., undefined global, in addition to t

Re: [Rd] Tips for debugging: R CMD check examples

2010-06-30 Thread Deepayan Sarkar
On Wed, Jun 30, 2010 at 3:26 AM, Hadley Wickham wrote: > Hi all, > > Does anyone have any suggestions for debugging the execution of > examples by R CMD check?  The examples work fine when I run them from > a live R prompt, but I get errors when they are run by R CMD check. 'R CMD check pkg' will

Re: [Rd] Tips for debugging: R CMD check examples

2010-06-30 Thread Gavin Simpson
[Apologies for breaking the thread, I deleted the message before starting this reply] Dear Hadley, R CMD check produces a foo-Ex.R file where foo is the package name. You could start by sourcing that file in R --vanilla and see where it fails and also use standard debugging tools in R from there

Re: [Rd] Tips for debugging: R CMD check examples

2010-06-30 Thread Tobias Verbeke
On 06/29/2010 11:56 PM, Hadley Wickham wrote: Does anyone have any suggestions for debugging the execution of examples by R CMD check? The examples work fine when I run them from a live R prompt, but I get errors when they are run by R CMD check. Not a real tip, but when it occurs I immediate