Displaying 20 results from an estimated 300 matches similar to: "Small program embedding R crashes in 64 bits"
2018 Feb 13
0
R Compilation gets stuck on Windows 64
Hi Avraham,
I tried with the patched version. The same error message.
gcc -std=gnu99 -m64 -shared -s -mwindows -o R.dll R.def console.o dynload.o
editor.o embeddedR.o extra.o malloc.o opt.o pager.o preferences.o psignal.o
rhome.o rt_complete.o rui.o run.o shext.o sys-win32.o system.o dos_wglob.o
dllversion.o ../main/libmain.a ../appl/libappl.a ../nmath/libnmath.a
getline/gl.a
2018 Feb 13
2
R Compilation gets stuck on Windows 64
On Tue, Feb 13, 2018 at 12:22 PM, Indrajit Sen Gupta
<indrajitsg at gmail.com> wrote:
> Hi Avraham,
>
> I tried with the patched version. The same error message.
>
> gcc -std=gnu99 -m64 -shared -s -mwindows -o R.dll R.def console.o dynload.o
> editor.o embeddedR.o extra.o malloc.o opt.o pager.o preferences.o psignal.o
> rhome.o rt_complete.o rui.o run.o shext.o
2018 Feb 13
0
R Compilation gets stuck on Windows 64
I was able to compile the R from the github by running build-r-devel.bat!
Now need to see how to compile it with BLAS.
Regard,
Indrajit
On Tue, Feb 13, 2018 at 5:45 PM, Jeroen Ooms <jeroenooms at gmail.com> wrote:
> On Tue, Feb 13, 2018 at 12:22 PM, Indrajit Sen Gupta
> <indrajitsg at gmail.com> wrote:
> > Hi Avraham,
> >
> > I tried with the patched
2018 Feb 13
2
R Compilation gets stuck on Windows 64
In the file MkRules.local.in, I see the line: USE_ATLAS = NO which I
believe needs to be changed to YES. But how do I specify the BLAS file
*libopenblas_haswell-r0.2.20.a
*and its location?
Regards,
Indrajit
On Tue, Feb 13, 2018 at 6:41 PM, Indrajit Sen Gupta <indrajitsg at gmail.com>
wrote:
> I was able to compile the R from the github by running build-r-devel.bat!
>
> Now need
2020 Mar 11
0
R CMD INSTALL cannot recognize full path on Windows
Thanks a lot for your suggestions. I see what you mean. I have removed all
unnecessary files and dependences on https://github.com/Jiefei-Wang/example,
but still no luck. I've tried to install the package as a user, not admin,
but I got the same error. Also, I apologize for spamming the mail list. I
will keep my reply as neat as possible.
Martin has suggested checking the encoding of the file
2019 Feb 16
3
Trying to compile R 3.5.2 - 32 bit R - on Windows 10 64 bit - with ICU support
Hi,
I am trying to compile R with ICU support.
I am following
https://cran.r-project.org/doc/manuals/R-admin.html#Building-from-source
I have downloaded and extracted
https://www.stats.ox.ac.uk/pub/Rtools/goodies/ICU_531.zip
to
W:\R-3.5._\App\R-Portable\ICU
I have modified MkRules.local
# set to use ICU
USE_ICU = YES
# path to parent of ICU headers
ICU_PATH = w:/R-3.5._/App/R-Portable/ICU
I
2018 Feb 09
2
R Compilation gets stuck on Windows 64
Hi All,
I am trying to compile R from source on a 64 bit Windows. I have downloaded
and installed all the third party software as per the R - documentation.
The compilation starts fine and after a while it stops with the following
error message:
D:/Rtools/mingw_64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.3/../../../../x86_64-w64-mingw32/bin/ld.exe:
cannot find -lRgraphapp
collect2.exe: error: ld
2020 Mar 11
1
R CMD INSTALL cannot recognize full path on Windows
Jiefei,
you did not commit all files into the example package - your example has things like RcppExports.cpp as well as additional flags which are not in your GH project. I suspect the issue is with the extra flags you're adding - those don't come from R. Please make sure you can replicate the issue with the GH package you created.
Cheers,
Simon
* installing *source* package
2003 Aug 01
1
samba 3.0 beta3 ldapsam bug ?!?!
Thanks for your help in adance !!!
I work with SAMBA HEAD since alpha24. I have running a BDC, PDC, Printserver on 3
separate pc's. In my domain is integrated a nativ w2k Fileserver ( Dell Nas PowerVault
725 ) for fileserving. Passwords are held in LDAP on every (Linux) machine pam-ldap
works. Every thing was fine before the last update to BETA 3.
Problem :
I was updating from BETA 2 to
2012 Jun 24
2
Win 64 package build - ERROR: loading failed for 'x64'
I have developed an R package that works under Win32, but when I attempt to build it on Win64,
I get ERROR: loading failed for 'x64'
More precisely, I developed and tested the package under Win32 and it works. But when I move
to a 64 bit Windows 7 (Home Premium) system, and attempt to build both 32 bit and 64 bit packages,
the 32 bit package seems to build, but the 64 bit build
1997 Nov 06
1
R-alpha: "invisible" (yet again): a more problematic bug[let]
I think this is a more problematic buglet
in (implicit/explicit) ``invisible behavior'').
Try this (all versions of R from 0.49 to 0.60):
test0 <- function() c(1,2)
test <- function(two = FALSE) c(1, if(two) 2)
testR <- function(two = FALSE) return(c(1, if(two) 2))
test0()# 1 2 as it should
test() #
1999 Sep 14
1
dyn.load
Hello,
I have a probleme with the dynamic loading. I make
two librairies "myfct.so" and "otherfct.so", where
"myfct.so" is calling functions of "otherfct.so",
and I want dyn.load() each of it, without generating
a unique librarie. For exemple :
myfct.c :
void myfct(double *x, double *y)
{
otherfct(x);
*y=(*x)+1.0;
}
myoth.c :
void otherfct( double *x
2018 Feb 09
0
R Compilation gets stuck on Windows 64
Hi Avraham,
A quick question - I realized I did not have *Perl* installed. So I
installed *ActiveState Perl* right now. Also I see I need *texinfo* and
*texi2any*. I was able to installed *texinfo* from here:
http://gnuwin32.sourceforge.net/packages/texinfo.htm. But not sure where to
get *texi2any*. Can you guide me in this step?
Regards,
Indrajit
On Fri, Feb 9, 2018 at 11:58 AM, Indrajit Sen
2017 Jun 03
0
cygwin1.dll problems when installing packages from source
On 03/06/2017 6:31 AM, Vivek Sutradhara wrote:
> Hi all,
> I am having some problems in updating some packages from source. I start
> with :
> install.packages("Boom",lib="C:/RownLib",type="source")
>
> I get the following error message :
Do you have multiple copies of cygwin1.dll?
Duncan Murdoch
>
> * installing *source* package
2017 Jun 03
0
cygwin1.dll problems when installing packages from source
On 03/06/2017 7:00 AM, Vivek Sutradhara wrote:
> Hi,
> As far as I can see, no.
>
> On checking, I have confirmed that the only location of
> cygwin1.dll is :
> C:\Rtools\bin
I would re-install Rtools, and make sure C:\Rtools\bin appears first in
your PATH.
Duncan Murdoch
>
> Thanks
> Vivek
>
> 2017-06-03 12:57 GMT+02:00 Duncan Murdoch <murdoch.duncan at
2003 Sep 22
1
creates directory that can't be deleted (PR#4246)
Full_Name: Xiaobao Wang
Version: R 1.7.1
OS: Windows XP
Submission from: (NULL) (24.45.25.102)
accidentally done the following:
rpt.dir <- paste("c:/report/testR","bestsub",spe="/")
dir.create(rpt.dir)
(spe should be sep). Now the directory "c:/report/testR bestsub " cannot be
removed. I tried to remove it from Windows Explorer and got the message
2008 Mar 27
1
Nothing happened when I using t.test throuth RSPerl
Hi,
I've just started using RSPerl. Though also tests in directory "/usr/local/lib/R/library/RSPerl/tests/" are passed successfully, I meet the problem with the following codes;
use strict;
use warnings;
use R;
use RReferences;
my @array1=1..10;
my @array2=1..39;
&R::initR("--silent");
&R::library("RSPerl");
my $tt=&R::call("t.test",
2017 Jun 03
3
cygwin1.dll problems when installing packages from source
Hi all,
I am having some problems in updating some packages from source. I start
with :
install.packages("Boom",lib="C:/RownLib",type="source")
I get the following error message :
* installing *source* package 'Boom' ...
** package 'Boom' successfully unpacked and MD5 sums checked
** libs
*** arch - i386
c:/Rtools/mingw_32/bin/g++ -std=gnu++11
2017 Jun 03
2
cygwin1.dll problems when installing packages from source
Hi,
As far as I can see, no.
On checking, I have confirmed that the only location of
cygwin1.dll is :
C:\Rtools\bin
Thanks
Vivek
2017-06-03 12:57 GMT+02:00 Duncan Murdoch <murdoch.duncan at gmail.com>:
> On 03/06/2017 6:31 AM, Vivek Sutradhara wrote:
>
>> Hi all,
>> I am having some problems in updating some packages from source. I start
>> with :
>>
2018 Feb 13
0
Setting the path to Rtools for package compilation on Windows
I can confirm the behaviour that you report.?
Usually I put Rtools in c:\programs\Rtools and modify the path
accordingly. Recently (don't recall for how long) I have encountered
the same problems as you have and I have resorted to moving Rtools to
c:\Rtools
I have no idea as how to proceed; perhaps it could be worth trying an
older version of Rtools (though that may cause other problems).