similar to: Segmentation fault early in compilation of revision 85514

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

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

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

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

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

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

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

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. ------------------------------ On Thu, Jan 8, 2015 2:01 PM GMT Henric Winell wrote: >On 2015-01-08 14:18, Avraham Adler

It seems that version of ICU_531 in <http://www.stats.ox.ac.uk/pub/Rtools/goodies/> as of June 25, 2014, was compiled using sjlj exception handling (current gcc-4.6.3, perhaps?). I say that as I am trying a 4.9.2 distribution which uses seh handling, and I get errors like: gcc -std=gnu99 -m64 -shared -s -mwindows -o R.dll R.def console.o dynload.o editor.o embeddedR.o extra.o malloc.o

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

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 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 :

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

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

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.

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

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

Hello, Could I please ask you for help? I opened a case in GCC Bugzilla and got reply that -fpie have to be used to get it compiled. Now it fails for me with: x86_64-pc-linux-gnu-gcc -o ssh ssh.o readconf.o clientloop.o sshtty.o sshconnect.o sshconnect1.o sshconnect2.o mux.o roaming_common.o roaming_client.o -L. -Lopenbsd-compat/ -flto=4 -fuse-linker-plugin -Wl,--as-needed -Wl,-O2 -Wl,-flto -O2

Am 31.05.2017 um 15:24 schrieb Timo Sirainen: > https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz > https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz.sig > > Due to some release process changes I didn't notice that one important bugfix wasn't included in the v2.2.30 release branch before I made the release. So fixing it here with v2.2.30.1. Also included another

> So starting a new Rcmd.exe process fails for some reason. > > If you take the same R session where the environment variables are > right and Sys.which() resolves Make and GCC and try to run > tools:::.shlib_internal(c('-n', 'hello.c')) or > tools:::.shlib_internal('hello.c'), does it do something useful? I think I tried the commands in the right R