Avraham Adler
2024-Oct-31 17:35 UTC
[Rd] Error compiling 87283 on Windows 10 using Rtools4.4 6335-6327
On Thu, Oct 31, 2024 at 12:42?PM Tomas Kalibera <tomas.kalibera at gmail.com> wrote:> > On 10/31/24 17:30, Avraham Adler wrote: > > When compiling R, the build fails after byte compiling grDevices with > > the following error: > > > > byte-compiling package 'grDevices' > > make[4]: *** [../../../share/make/lazycomp.mk:9: > > ../../../library/grDevices/R/grDevices.rdb] Error 139 > > make[3]: *** [Makefile.win:23: all] Error 2 > > make[2]: *** [Makefile.win:34: R] Error 1 > > make[1]: *** [Makefile:18: all] Error 2 > > make: *** [Makefile:392: distribution] Error 2 > > > > I restarted the build, as sometimes that allows it to power through, > > but it failed at the same point. Any thoughts or suggestions would be > > appreciated. > > Dear Avi, > > could you please post which compile options are you using? The vanilla > builds with default options are being tested regularly (and work). > > Best > TomasThank you, Tomas. Of course. Mkrules.local: USE_ATLAS = YES ATLAS_PATH = C:/R/OPB/OpenBLAS-0.3.28-5ef8b19 EOPTS = -march=native -pipe -mno-rtm -Wa,-muse-unaligned-vector-move LTO = -flto=1 -fuse-linker-plugin LTO_OPT = -flto=1 -fuse-linker-plugin LTO_FC = -flto=1 -fuse-linker-plugin LTO_FC_OPT = -flto=1 -fuse-linker-plugin QPDF = C:/R/qpdf-11.9.1-msvc64 OPENMP = -fopenmp And, of course, blas/Makefiles.win has been patched to read the proper library, which I've been doing for over a decade. Thank you again!> > > > > This may be unrelated, but as I was monitoring the compilation, I saw > > an warning which I haven't seen before in the 20 or so years I've been > > building R on Windows: > > > > In function 'R_chk_memset', > > inlined from 'do_aperm' at ../main/array.c:1754:5: > > ../main/memory.c:3578:16: warning: 'memset' specified bound between > > 18446744056529682432 and 18446744073709551608 exceeds maximum object > > size 9223372036854775807 [-Wstringop-overflow=] > > 3578 | return n ? memset(s, c, n) : s; > > | > > > > No idea if it is related but I thought I should mention it. > > > > > Thank you, > > > > Avi > > > > ______________________________________________ > > R-devel at r-project.org mailing list > > https://stat.ethz.ch/mailman/listinfo/r-devel
Tomas Kalibera
2024-Oct-31 18:06 UTC
[Rd] Error compiling 87283 on Windows 10 using Rtools4.4 6335-6327
On 10/31/24 18:35, Avraham Adler wrote:> On Thu, Oct 31, 2024 at 12:42?PM Tomas Kalibera > <tomas.kalibera at gmail.com> wrote: >> On 10/31/24 17:30, Avraham Adler wrote: >>> When compiling R, the build fails after byte compiling grDevices with >>> the following error: >>> >>> byte-compiling package 'grDevices' >>> make[4]: *** [../../../share/make/lazycomp.mk:9: >>> ../../../library/grDevices/R/grDevices.rdb] Error 139 >>> make[3]: *** [Makefile.win:23: all] Error 2 >>> make[2]: *** [Makefile.win:34: R] Error 1 >>> make[1]: *** [Makefile:18: all] Error 2 >>> make: *** [Makefile:392: distribution] Error 2 >>> >>> I restarted the build, as sometimes that allows it to power through, >>> but it failed at the same point. Any thoughts or suggestions would be >>> appreciated. >> Dear Avi, >> >> could you please post which compile options are you using? The vanilla >> builds with default options are being tested regularly (and work). >> >> Best >> Tomas > Thank you, Tomas. Of course. > > Mkrules.local: > USE_ATLAS = YES > ATLAS_PATH = C:/R/OPB/OpenBLAS-0.3.28-5ef8b19 > EOPTS = -march=native -pipe -mno-rtm -Wa,-muse-unaligned-vector-move > LTO = -flto=1 -fuse-linker-plugin > LTO_OPT = -flto=1 -fuse-linker-plugin > LTO_FC = -flto=1 -fuse-linker-plugin > LTO_FC_OPT = -flto=1 -fuse-linker-plugin > QPDF = C:/R/qpdf-11.9.1-msvc64 > OPENMP = -fopenmp > > And, of course, blas/Makefiles.win has been patched to read the proper > library, which I've been doing for over a decade.Ok, could you please try the very same build (so the same version of R, same options, same external libs) with the previous version of Rtools44? Does that pass? Thanks Tomas> > Thank you again! > >>> This may be unrelated, but as I was monitoring the compilation, I saw >>> an warning which I haven't seen before in the 20 or so years I've been >>> building R on Windows: >>> >>> In function 'R_chk_memset', >>> inlined from 'do_aperm' at ../main/array.c:1754:5: >>> ../main/memory.c:3578:16: warning: 'memset' specified bound between >>> 18446744056529682432 and 18446744073709551608 exceeds maximum object >>> size 9223372036854775807 [-Wstringop-overflow=] >>> 3578 | return n ? memset(s, c, n) : s; >>> | >>> >>> No idea if it is related but I thought I should mention it. >>> Thank you, >>> >>> Avi >>> >>> ______________________________________________ >>> R-devel at r-project.org mailing list >>> https://stat.ethz.ch/mailman/listinfo/r-devel
Possibly Parallel Threads
- Segmentation fault early in compilation of revision 85514
- Change between 86152 and 86534 - probably 86265 - that looks for zspmv in BLAS and not LAPACK causes R with OpenBLAS to fail
- R Compilation gets stuck on Windows 64
- Problems with building R from sources
- R Compilation gets stuck on Windows 64