On Tue, 26 May 2015, Daniel Kelley wrote:
Roger,
I plan to make the next version of oce use rgdal::project() to do its
work. The idea of using an external PROJ.4 is fine in my own work, but
oce has a lot of users who are unaccustomed to building and installing
external libraries. Also, many
Hi all,
Thanks for your suggestions.
1. As I said, the the same package code was running was R.3.1.2 earlier
and giving no errors... so not sure if it has to do with the package code
2. We checked the permissions issue, with the admin running it and it
still stalled at the same place
3. Finall
Roger,
I plan to make the next version of oce use rgdal::project() to do its work. The
idea of using an external PROJ.4 is fine in my own work, but oce has a lot of
users who are unaccustomed to building and installing external libraries. Also,
many work at institutes that do not permit this ki
Dan,
I'm sorry to be late to the party (one is offline occasionally), but all
the advice given so far is at best only partially correct.
Use of PROJ.4 is crucially conditional on access to PROJ_LIB a shell
variable setting the address of metadata files not included in the C
source. PROJ.4 wi
On 26.05.2015 17:33, Dirk Eddelbuettel wrote:
On 26 May 2015 at 07:04, Charles Determan wrote:
| That is strange the R CMD check is stalling but there didn't appear to be
| any attached screenshot. I would be also beneficial if we could see/access
We don't do screenshots, and we don't do htm
On 26 May 2015 at 07:04, Charles Determan wrote:
| That is strange the R CMD check is stalling but there didn't appear to be
| any attached screenshot. I would be also beneficial if we could see/access
We don't do screenshots, and we don't do html email.
| your source code. Is your package hos
Hi Pieter,
search for 'Rprintf' in the 'Writing R extensions' manual:
http://cran.r-project.org/doc/manuals/r-release/R-exts.html
Gabor
On Tue, May 26, 2015 at 9:55 AM, Pieter Eendebak
wrote:
> Dear developers,
>
> For an R package I am including some code I have written previously which
> use
Dear developers,
For an R package I am including some code I have written previously which
uses stdout, stderr and printf. The command R CMD check [packagename] gives
me warnings about these items. What is the proper way to print output in an
R package?
The documentation mentions that output is s
Hi Chaitanya,
That is strange the R CMD check is stalling but there didn't appear to be
any attached screenshot. I would be also beneficial if we could see/access
your source code. Is your package hosted on GitHub or a similar service?
Regards,
Charles
On Mon, May 25, 2015 at 10:42 PM, Chaitan
I was afraid so. In some of the previous exchanges, Martyn Plummer apparently
offered help, but this was for solaris-x86, not sparc.
Heck, many years ago, I used to own a SPARCstation 20 -- not that it would run
Solaris 10 (need an ultrasparc for that). I even started browsing a couple days
ago
Thanks for the reply, Ben.
Excluding Solaris from (some of the) tests is of course one (rather
brute-force) way of circumventing the issue. And in fact, if I hadn't been able
to resolve the errors, I probably would have taken that shortcut as well. On
the other hand, if this would become common
Hi There,
Can you please help me with this query please?
Thanks in advance,
Chaitanya
Dr. Chaitanya Joshi
Senior Lecturer,
Department of Statistics,
University of Waikato,
Hamilton, New Zealand.
Webpage: www.cms.waikato.ac.nz/~cjoshi
Office: G3.29
Phone: +64 7 838 4019
On 24/05/2015 8:48 a.m
12 matches
Mail list logo
