I am trying to build a C language DLL and it works well with i386 but when I
compile with it substituted
by x64, like the FAQ page says, the result is an error message:
C:/PROGRA~1/R/R-214~1.0/bin/x64/R.ddl: file not recognized : File format not
recognized
collect2: ld returned 1 exit status
H
What is R.ddl? Or is that not the actual output?
In any case, it isn't going to work unless you run 64-bit 'R', and
my guess is that you used 32-bit 'R' to do this. Make sure you use
/bin/x64/R CMD
and you do not need the -L
On Mon, 12 Dec 2011, ruipbarra...@sapo.pt wrote:
I am
All,
When building a package, how can I suppress startup messages of package
imports? I know you can use suppressPackageStartupMessages() around
library or require when loading a package, but can I set in NAMESPACE or
DESCRIPTION (or elsewhere?) to suppress any startup messages from imported
pack
In a vanilla R 2.14.0 GUI session (on Windows XP SP3):
> library(parallel)
> cl<-makePSOCKcluster(2)
> RNGkind()
[1] "Mersenne-Twister" "Inversion"
> clusterSetRNGStream(cl)
> RNGkind()
[1] "L'Ecuyer-CMRG" "Inversion"
> stopCluster(cl)
Is it intentional that clusterSetRNGStream() changes the RNG
On 12.12.2011 14:12, ruipbarra...@sapo.pt wrote:
I am trying to build a C language DLL and it works well with i386 but when I
compile with it substituted
by x64, like the FAQ page says, the result is an error message:
C:/PROGRA~1/R/R-214~1.0/bin/x64/R.ddl:
What is R.ddl? Do you mean R.dll?
Prof. Ripley,
Thank you for your suggestion.
In the mean time, I had just found a solution and was going to send a
mail saying that the problem was solved
when I read your answer, and others.
The 'ddl' is obviously not the actual output, DOS doesn't allow copy&paste.
The solution is to use th
On 12.12.2011 21:12, ruipbarra...@sapo.pt wrote:
Prof. Ripley,
Thank you for your suggestion.
In the mean time, I had just found a solution and was going to send a
mail saying that the problem was solved
when I read your answer, and others.
The 'ddl' is obviously not the actual output, DOS
With some chagrin after spending a couple of hours trying to debug a script, I
realized I
had typed in something like
ans<-optimx(start, myfn, mygr, lower<-lo, upper=up)
that is, the "<-" rather than "=". The outcome on my machine was a non-obvious
error
several layers deep in the call stack. F
This is valid syntax, so what should we check for?.
Uwe
On 12.12.2011 22:10, John C Nash wrote:
With some chagrin after spending a couple of hours trying to debug a script, I
realized I
had typed in something like
ans<-optimx(start, myfn, mygr, lower<-lo, upper=up)
that is, the "<-" rather
