similar to: Building Rblas.dll failing on Windows 7 (64-bit)

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

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

Executive summary: I believe revision 86265 makes it more difficult to build R with OpenBLAS on Windows as now the entire LAPACK needs to be built to obtain zspmv. Is there anything that can be done to allow the former behavior to be used, something in Mkrules.local perhaps? Detailed Explanation: I have been building R with OpenBLAS for Windows 64 for over a decade by patching

Ok, moved to R-devel. I tried to build R-2.3.1. Since I intent to distribute this tuned R to all other who have a computer like mine here at work I thought it was best to stay with the latest stable release. About your suggestion, I could'n find xerblas.o file. And I don't know how to edit libf77blas.a. I tried to open it with VIM (http://vim.sf.net/) but there was a lot of strange

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

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

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

Hello list, I would like to cross-compile R packages using R 2.4.0. I am working on Linux Debian and cross-compiled (windows binaries) without problems with older R version. I have used the doc of Yan and Rossini in the contributed section of the R documentation (same version of MinGW...). When I try to cross-compile R (make R), the procedure stopped and returns :

I think this is not a R-devel question. Sorry to all if I'm wrong, please let me know. I managed to build R successfully with the default BLAS but when I change the MKRULES to use ATLAS BLAS and set the path to "C:/cygwin/home/Administrador/ATLAS/lib/WinNT_ATHLONSSE2" I got the following error message (I'm posting only the final part, there was a lot of compilation before this):

Hi, for diagnostic purposes, I would like to get information about the BLAS / LAPACK linked against R from within an R-session. An obvious application could be safety-checks for packages like Matrix and quantreg at load / attach - time. Also you could be more precise on the "framework" in which R is running for comparable benchmark timings on different systems. Perhaps this

Dear Windows Maintainers, after installing R 2.6.0 on Windows 2000 and doing a complete update of the libraries as recommended by B.Ripley, it get the error message: The dynamic link library Rblas could not be found in the specified path.... Note that the message says "Rblas", not Rblas.dll as expected under Windows. The path is correct, and Rblas.dll is present I made a copy of

I encountered the following problem in R-2.4.0 for Windows binary downloaded from CRAN (data from R-help post by Ethan Johnsons). I was also using the contributed binary Rblas.dll for Intel P4 chip. The problem doesn't occur with the default Rblas.dll. x=c(3.05176E-05, 0.000457764, 0.003204346, 0.0138855, 0.04165649, 0.09164429, 0.1527405, 0.1963806, 0.1963806, 0.1527405, 0.09164429,

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

hi everyone, Im implementing a new RBlas dll but just for optimising sake i need to know how and WHERE (which source code) RBlas gets loaded. there is a call to loadlibrary() in dynload.c BUT it seems this is not the function that is loading Rblas. how do i know this? well i added the code :(just after the loadlibrary() call) /*********************************************/ /*this

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

There is a new area on CRAN bin/windows/contrib/ATLAS which contains Rblas's compiled against ATLAS 3.4.1 for various chips. To use one of these, just rename rw1051\bin\Rblas.dll and drop the replacment in its place. Using a tuned BLAS will be noticeably faster only on some linear-algebra calculations, notably those using La.svd and La.eigen (which might be twice as fast). There are

Dear Prof. Ripley, thank you very much. It works now absolutely fine using a "Makevars" file with the contents you suggested. Thanks again, Roland > -----Original Message----- > From: Prof Brian Ripley [mailto:ripley at stats.ox.ac.uk] > Sent: Thursday, March 09, 2006 12:09 PM > To: Rau, Roland > Cc: r-help at stat.math.ethz.ch > Subject: Re: [R] Linking Rblas

I noticed a problem using R 2.7.1 on Windows XP SP2 with the precompiled Atlas Rblas.dll. Running the code below causes R to crash. I started R using Rgui --vanilla and am using the precompiled Atlas Rblas.dll from cran.fhcrc.org dated 17-Jul-2007 05:04 for Core2 Duo. The code that causes the crash: x <- rnorm(100) y <- rnorm(100) z <- rnorm(100) loess(z ~ x * y) loess(z ~ x) does

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