On 10/18/2010 10:00 PM, Dominick Samperi wrote:
>
> The procedure for creating an import library (Rdll.lib) that is documented
> in gnuwin32/README.packages works fine using the i386 architecture, but
> it doesn't seem to work under x64.
>
> Specifically, the procedure is:
> pexports R.dll > R.ex
Michael Sumner-2 wrote:
>
> I think there's something about the "discrete cell" versus "centre value"
> interpretation here, and you are pushing the "pixels" through R's graphics
> engine as well as whatever the png device has to do.
>
> I can't enlighten you about the details of that, but by c
Thanks Joe, obviously I made the error of including R.dll on the command
line,
sorry for the wasted bandwidth.
On Tue, Oct 19, 2010 at 1:22 AM, Joe Conway wrote:
> On 10/18/2010 10:00 PM, Dominick Samperi wrote:
> >
> > The procedure for creating an import library (Rdll.lib) that is
> documented
Hello,
The procedure for creating an import library (Rdll.lib) that is documented
in gnuwin32/README.packages works fine using the i386 architecture, but
it doesn't seem to work under x64.
Specifically, the procedure is:
pexports R.dll > R.exp
lib /def:R.exp /out:Rdll.lib /machine:X86 R.dll
Ther
Is it possible to suppress compiling for the x64 arch when doing 'Rcmd
build ? Such that the pre-compiled package for binary
distribution only contains a 'lib/i386/mypkg.dll'.
For CHECK (and also INSTALL) there is a '--no-multiarch' argument, but
I didn't find something similar for build.
Otherwi
I find system.file() handy for writing examples,
but if the user mistypes its arguments or if a
package is not up to date its return value of ""
can lead to trouble. This forces the example to
be wordier than I'd like.
E.g., the following example works
> scan(what="", sep="\n", system.file("DES
On 10/18/2010 01:07 PM, Philippe Grosjean wrote:
Thanks anyway for all your work on R-Forge... We will probably survive
this thread ;-)
Once you will got an hardware upgrade, I think we will all be happy to
recover complete testing of developed packages (Linux 32/64bit, Mac
32/64bit, Windows 32
Thanks anyway for all your work on R-Forge... We will probably survive
this thread ;-)
Once you will got an hardware upgrade, I think we will all be happy to
recover complete testing of developed packages (Linux 32/64bit, Mac
32/64bit, Windows 32/64bit), ... if possible.
Best,
Philippe
..
On 10/16/2010 10:27 AM, Ben Bolker wrote:
anyone have a status report on r-forge ... ?
From here (Hamilton, ON) I can't ping ...
PING r-forge.wu-wien.ac.at (137.208.57.38) 56(84) bytes of data.
The machine was restarted today morning. We are sorry for the downtime.
We need to migrat
On 10/18/2010 02:39 AM, Radford Neal wrote:
> Regarding Tengfei Yin's post about an error trying to install
> "cluster" in 2.13.0, I have gotten an error with this package when
> trying to install the released version of 2.12.0. Here is the output
> on an Ubuntu Linux system:
Hmm, g77 along with
10 matches
Mail list logo