similar to: Cross-compilation of R and ld bug ?

I have the same problem, trying to cross-compile. I'm running Ubuntu Edgy, kernel 2.6.17-10-generic, on an IBM T60. I downloaded the Makefile from CRAN and ran make CrossCompileBuild with the following error messages (also ran each make one at the time and the problem occurs in make R): ../extra/pcre/libpcre.a(pcre_dfa_exec.o):pcre_dfa_exec.c:(.text+0x1703): undefined reference to

Hello, I was trying to build R from source on Windows XP. I installed software which are mentioned from the follow web page http://www.murdoch-sutherland.com/Rtools/ (Last accessed on Nov. 13th, 2006) . Unfortunately, I got error messages whenever I run 'make all recommended' without modifying 'MkRules' file. I have removed software and reinstalled them several times but I still

Dear all, I already posted a question regarding this to an existing thread: http://tolstoy.newcastle.edu.au/R/e2/devel/06/10/0852.html#start I apologize for the double posting but I have some further information that might be illuminating. I am trying to cross-compile my R-package under ubuntu linux, kernel 2.6.17-10-generic, on an IBM T60. I am following the suggested steps in

Hi, I tried to compile R-2.10.0 src on 64 bit window. After install Rtools and wingw-w64 compiler and put it the first of my PATH variable, but i got the following error when i tried to compile. Anything I missed? thank you. x86_64-w64-mingw32-gcc -std=gnu99 -I../include -I. -I../extra -DHAVE_CONFIG_H -D R_DLL_BUILD -O3 -Wall -pedantic -DR_ARCH='"x64"' -c malloc.c -o

Dear R People: I'm trying to compile R-2.15.0 on a 64 bit Windows machine. However, I'm getting the following error: c:\R64\R-2.15.0\src\gnuwin32>set TMPDIR=c:\temp set TMPDIR=c:\temp c:\R64\R-2.15.0\src\gnuwin32>make all recommended make all recommended make[1]: `MkRules' is up to date. make[4]: Nothing to be done for `svnonly'. installing C headers make[2]: Nothing to

Dear R People: I am trying to build R-2.5.0 from source on a Windows machinee. I downloaded the tools and such, and started things off. I received some odd errors messages, looked on the R Search and found a similar problem. The suggestion was to re-load "ld.exe". I downloaded and installed everything again. Same problem. I am including my output.

Hello! I'm trying to install R-patched from source on a Windows 64 bit laptop. I have installed R-tools 2.16 and set up the jpeg, tiff, and libpng files Here is the output: c:\R64\R-patched\src\gnuwin32>make all recommended make all recommended make[1]: `MkRules' is up to date. make[4]: Nothing to be done for `svnonly'. installing C headers make[2]: Nothing to be done for

Hello all, I'm trying to build R 32bit from source in a Windows 64 machine. I have followed the steps in "R Installation and Adiministration" ( http://cran.r-project.org/doc/manuals/R-admin.html#Getting-the-source-files) or at least I think I did everything described. I am not sure if I have installed the libjpeg, libtiff and libpng files though. I have upzipped them in the

On Thu Jan 9 2014 03:47 Henrik Bengtsson wrote: > This is is an issue that bugged me for a while. I encountered a year > ago (April 2012) when I first tried to build R from source on Windows. > I never figured out what the solution is or if I'm doing something > wrong myself (but I have found a tedious workaround). I'm still on > the same Windows 7 Ultimate machine with

Oh, I forgot to mention that besides setting AR, RANLIB and the stack probing fix, you also need a very up to date binutils. 2.25 was out in december. Even with that , if you linker's default is not what you are compiling for (i.e. a multiarch toolchain), you need to set GNUTARGET also, i.e. -m32/-m64 is not enough. Some fix to autodetect non-default targets went in after christmas before the

I get the following error when building R from the subversion server as well as the latest tarball. I am on Windows XP, and I recently updated my MinGW installation. It's quite possible I am doing something wrong, but I am not sure what that might be. making console.d from console.c making dataentry.d from dataentry.c making dynload.d from dynload.c making edit.d from edit.c making editor.d

I'm currently attempting to build R-2.10.1 from the source on Windows 7 (64-bit version). I've downloaded the latest Rtools (Rtools211.exe) from the Murdoch-Sutherland site and have done a full install. I've also downloaded the HTML Help Workshop, MikTeX, and the InnoSetup installer. I am not using any 64-bit versions of the tools, such as the MinGW-w64, or a 64-bit version of TCL

Very timely, as this is how I got into the problem I posted about earlier; maybe some of the problems I ran into will mean more to the you and the experts on this thread, Dr. Murdoch.For reference, I run Windows 7 64bit, and I am trying to build a 64 bit version of R-3.1.2. As we discussed offline, Dr. Murdoch, I've been trying to build R using more recent tools than GCC4.6.3 prerelease.

When updating to the very last version of RODBC under freebsd 6.1 the errors below pop up but RODBC compiles till the end and, it seems, to work properly. What are those errors about? Vittorio .............................................. checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... grep: error while

Hi, I'm trying to build R on windows and i'm getting the following error when i run the "make all recommended" command: C:/Rtools/mingw_64/bin/windres -F pe-x86-64 -i dllversion.rc -o dllversion.o comm: file 1 is not in sorted order make[4]: *** [Rgraphapp.def] Error 1 make[3]: *** [rlibs] Error 1 make[2]: *** [../../bin/x64/R.dll] Error 2 make[1]: *** [rbuild] Error 2 make:

Compilation of MCMCpack under freebsd 6.2 i386 fails because of the following cryptic error: * Installing *source* package 'MCMCpack' ... checking for C++ compiler default output file name... a.out checking whether the C++ compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we

This is is an issue that bugged me for a while. I encountered a year ago (April 2012) when I first tried to build R from source on Windows. I never figured out what the solution is or if I'm doing something wrong myself (but I have found a tedious workaround). I'm still on the same Windows 7 Ultimate machine with NTFS, but I now made sure I started from scratch so I have a completely

On Thu, Jan 8, 2015 at 10:48 AM, Hin-Tak Leung <htl10 at users.sourceforge.net> wrote: > > The r.dll crash is easy - you need to be using gcc-ar for ar, and gcc-ranlib for ranlib. I also posted a patch to fix the check failure for stack probing, as lto optimizes away the stack probing code, as it should. > > yes, lto build's speed gain is very impressive. > > I

We're trying to setup 3 PRDM partitions (VMware) across 2 nodes. As long as only one is configured in cluster.conf, there's not problem. As soon as we try to use 2 or more we get issues. It looks the same as bug 636: http://oss.oracle.com/bugzilla/show_bug.cgi?id=636 I posted my cluster.conf and command line results there. I'm including them here in the hopes that someone on this

Good evening. Testing the most recent version of Rtools, the build stops about when text.c is being compiled in the tools package (just after R.Lapack). The compilation is looking for gcc in C:, even though RTOOLS is set for another drive, and the compilation has successfully run until this point. This did not happen last night with version 1955. I've uninstalled and reinstalled Rtools three