All--
Does anyone know if the update from R 2.15.2 to 3.0 is likely to change
they way these binaries would need to be built? I don't think that the
NAMESPACE .First.lib changes will matter, but I don't understand the
implications of long.vectors. http://developer.r-project.org/30update.txt
On Mon, 11 Feb 2013, Tom Philippi wrote:
All--
Does anyone know if the update from R 2.15.2 to 3.0 is likely to change
they way these binaries would need to be built? I don't think that the
NAMESPACE .First.lib changes will matter, but I don't understand the
implications of long.vectors.
Ista,
Sorry about lack of detail. Here are a some additional specifics:
- this is for Windows (only). I'm aware the libraries exist for Linus,
MacOX, etc but we're a Windows shop.
- R: We've been struggling with this in ver 2.14 to the current (2.15.2).
It's not a version issue.
Two
Hi John,
Looks like a PITA. I gave it a try without any success. All I can
suggest is that you very carefully document your build attempts, and
post only very specific questions, including exactly what you did and
the exact error messages.
Honestly if I were you I would just do this in Linux.
Yep. That's what the developers tell me. I'm grateful they've been willing
to work on this, saving me the pain. When the one working on this returns,
I'll post more precise info on the issues and error messages. The Unidata
site makes it look simple, but it obviously is not.
Thanks for having
Bump. Still wondering if anyone can help.
--
View this message in context:
http://r-sig-geo.2731867.n2.nabble.com/64-bit-ncdf4-for-Windows-tp7582474p7582540.html
Sent from the R-sig-geo mailing list archive at Nabble.com.
___
R-sig-Geo mailing list
Hi John,
On Fri, Feb 8, 2013 at 5:44 PM, JohnG john_gr...@nps.gov wrote:
Bump. Still wondering if anyone can help.
You haven't given us much to go on. What happened when you tried
building the package? What error messages did you get? What version of
R are you using? What version of the ncdf
