[R-pkg-devel] ERROR building MixAll on Windows platform
This post is a continuation of the post *[R-pkg-devel] Does dependencies up to date on the pretest
CRAN infrastructure*
I made more (unsuccessful) tries:
- I installed a Windows 11 version in a VM on my compuiter and try to buid the MixAll package using
Rtools42 and Rtools43 (it's quite easy, and funny, to do it on windows: you have just to rename
C:\rtools42 as C:\rtools43).
The result is that MixAll is build using the 4.2 version and the buid failed
using the 4.3 version.
- I installed the version 12.3 of gcc on ubuntu (the same version used on windows) and could build
the package without problem
- Inspecting the log of the Rtools4.3
(https://cran.r-project.org/bin/windows/Rtools/rtools43/news.html) and g++12..3
(https://gcc.gnu.org/gcc-12/changes.html) does not give insight.
- The package is dependent of the rtkore package which use extensive use of templated class. As
rtkore is a port for R of stk++, I try to compile the stk++ library on windows (using g++12). All
tests are compiled without any troubles.
These attempts eliminate some causes, but don't give me any insight why MixAll (and blockcluster)
failed to be build on the Windows-devel platform. It seems related to Rtools43. Does anyone else
(using for exemple Rcppeigen) is experiencing this problem ?
Serge
Le 14/01/2024 à 18:50, Uwe Ligges a écrit :
On 13.01.2024 15:01, Uwe Ligges wrote:
Fascinating, now it worked with the latest winbuilder submission 3 times in a row when I checked
it manually. So maybe Ivan was right and there was a very demanding set of other packages
compiling at the same time?
I don't know.
Serge, Can you somply submit your latest winbuilder upload to CRAN?
Really, I inspected some more. The underlying issue is simple:
The C++ compiler used under Windows asks for precomitted memory. If several processes are running at
the same time, a lot of memory is precomitted. And Windows does not use it for other processes, even
if almost nothing is actually used.
So while the used memory may be around 50GB, all of the rest (of 756 GB including swap space) may
have been precomitted (but unused) and new processes failed to start correctly. G.
Best,
Uwe Ligges
Best,
Uwe Ligges
On 13.01.2024 14:12, Uwe Ligges wrote:
I can take a look, but not sure if I get to it before monday.
I haven't seen it for any other packages recently.
My suspicion is currently a strange mix of cmd.exe and sh.exe calls. But this
is a very wild guess.
Best,
Uwe
On 13.01.2024 14:08, Uwe Ligges wrote:
On 13.01.2024 10:10, Ivan Krylov via R-package-devel wrote:
В Fri, 12 Jan 2024 21:19:00 +0100
Serge пишет:
After somme minor midficiations, I make a try on the winbuilder site.
I was able to build the archive with the static library
but I get again a Bad address error. You can have a look to
https://win-builder.r-project.org/bw47qsMX3HTd/00install.out
I think that Win-Builder is running out of memory. It took some
experimenting, but I was able to reproduce something like this using
the following:
1. Set the swap file in the Windows settings to minimal recommended
size and disable its automatic growth
2. Write and run a program that does malloc(LARGE_NUMBER); getchar();
so that almost all physical memory is allocated
3. Run gcc -DFOO=`/path/to/Rscript -e 'some script'` & many times
I got a lot of interesting errors, including the "Bad address":
Warnings:
1: .getGeneric(f, , package) : internal error -4 in R_decompress1
2: package "methods" in options("defaultPackages") was not found
0 [main] bash (2892) child_copy: cygheap read copy failed,
0x0..0x800025420, done 0, windows pid 2892, Win32 error 299
0 [main] bash (3256) C:\rtools43\usr\bin\bash.exe: *** fatal error in
forked process - MEM_COMMIT failed, Win32 error 1455
-bash: fork: retry: Resource temporarily unavailable
-bash: R-devel/bin/Rscript.exe: Bad address
The above indeed happens if not sufficient memory would be available.
Important to know: This includes unused but committed memory which may be a lot.
But I doubt it is the case on winbuilder as the machines has 256GB or more (depending in the
machine) and additionally 500GB swap space on SSD.
Best,
Uwe
Your package is written in C++, but that by itself shouldn't disqualify
it. On my Linux computer, /usr/bin/time R -e
'install.packages("MixAll")' says that the installation takes slightly
less than a gigabyte of memory ("912516maxresident k"), which is par
the course for such packages. (My small Rcpp-using package takes
approximately half a gigabyte by the same metric.)
I'm still not 100% sure (if Win-Builder is running out of memory, why
are you seeing "Bad address" only and not the rest of the carnage?),
but I'm not seeing a problem with your package, either. If EFAULT is
Cygwin's way of saying "I caught a bad pointer in your system call"
(which, I must stress, is happening inside /bin/sh, not your
Re: [R-pkg-devel] Does dependencies up to date on the pretest CRAN infrastructure
Thank you both very much for your feedback.
I'll submit the package tomorrow and see...
Best,
Serge
Le 13/01/2024 à 15:01, Uwe Ligges a écrit :
Fascinating, now it worked with the latest winbuilder submission 3 times in a row when I checked it
manually. So maybe Ivan was right and there was a very demanding set of other packages compiling at
the same time?
I don't know.
Serge, Can you somply submit your latest winbuilder upload to CRAN?
Best,
Uwe Ligges
On 13.01.2024 14:12, Uwe Ligges wrote:
I can take a look, but not sure if I get to it before monday.
I haven't seen it for any other packages recently.
My suspicion is currently a strange mix of cmd.exe and sh.exe calls. But this
is a very wild guess.
Best,
Uwe
On 13.01.2024 14:08, Uwe Ligges wrote:
On 13.01.2024 10:10, Ivan Krylov via R-package-devel wrote:
В Fri, 12 Jan 2024 21:19:00 +0100
Serge пишет:
After somme minor midficiations, I make a try on the winbuilder site.
I was able to build the archive with the static library
but I get again a Bad address error. You can have a look to
https://win-builder.r-project.org/bw47qsMX3HTd/00install.out
I think that Win-Builder is running out of memory. It took some
experimenting, but I was able to reproduce something like this using
the following:
1. Set the swap file in the Windows settings to minimal recommended
size and disable its automatic growth
2. Write and run a program that does malloc(LARGE_NUMBER); getchar();
so that almost all physical memory is allocated
3. Run gcc -DFOO=`/path/to/Rscript -e 'some script'` & many times
I got a lot of interesting errors, including the "Bad address":
Warnings:
1: .getGeneric(f, , package) : internal error -4 in R_decompress1
2: package "methods" in options("defaultPackages") was not found
0 [main] bash (2892) child_copy: cygheap read copy failed,
0x0..0x800025420, done 0, windows pid 2892, Win32 error 299
0 [main] bash (3256) C:\rtools43\usr\bin\bash.exe: *** fatal error in
forked process - MEM_COMMIT failed, Win32 error 1455
-bash: fork: retry: Resource temporarily unavailable
-bash: R-devel/bin/Rscript.exe: Bad address
The above indeed happens if not sufficient memory would be available.
Important to know: This includes unused but committed memory which may be a lot.
But I doubt it is the case on winbuilder as the machines has 256GB or more (depending in the
machine) and additionally 500GB swap space on SSD.
Best,
Uwe
Your package is written in C++, but that by itself shouldn't disqualify
it. On my Linux computer, /usr/bin/time R -e
'install.packages("MixAll")' says that the installation takes slightly
less than a gigabyte of memory ("912516maxresident k"), which is par
the course for such packages. (My small Rcpp-using package takes
approximately half a gigabyte by the same metric.)
I'm still not 100% sure (if Win-Builder is running out of memory, why
are you seeing "Bad address" only and not the rest of the carnage?),
but I'm not seeing a problem with your package, either. If EFAULT is
Cygwin's way of saying "I caught a bad pointer in your system call"
(which, I must stress, is happening inside /bin/sh, not your package
or even R at all), it's not impossible that Win-Builder is having
hardware problems. Unfortunately, they take a lot of effort and
downtime to diagnose and could be hiding anywhere from RAM to the power
supply.
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] Does dependencies up to date on the pretest CRAN infrastructure
Hi Ivan, After somme minor midficiations, I make a try on the winbuilder site. I was able to build the archive with the static library but I get again a Bad address error. You can have a look to https://win-builder.r-project.org/bw47qsMX3HTd/00install.out Thanks for your help, Serge Le 12/01/2024 à 20:14, Ivan Krylov a écrit : В Fri, 12 Jan 2024 19:09:29 +0100 Serge пишет: I updated the package rtkore one month ago, fixing a compilation problem on windows devel platform. MixAll has a dependency to rtkore. Thus, I suspect that the error reported below is due to the presence of the old version of rtkore on the pretest infrastructure of the CRAN. <https://win-builder.r-project.org/incoming_pretest/MixAll_1.5.4_20240108_094228/Windows/00install.out>: /usr/bin/make -C projects/Clustering/src/ make[2]: Entering directory '/d/temp/RtmpYJkDTJ/R.INSTALL316dc7c0f48e6/MixAll/inst/projects/Clustering/src' g++ -std=gnu++17 -I"D:/RCompile/recent/R/include" -DNDEBUG `D:/RCompile/recent/R/bin/Rscript -e "rtkore:::CppFlags()"` -I'D:/RCompile/CRANpkg/lib/4.4/Rcpp/include' -I'D:/RCompile/CRANpkg/lib/4.4/rtkore/include' -I"d:/rtools43/x86_64-w64-mingw32.static.posix/include" `D:/RCompile/recent/R/bin/Rscript -e "rtkore:::CxxFlags()"` -I../inst/projects/ -I../inst/include/ -fopenmp -pedantic -O2 -Wall -mfpmath=sse -msse2 -mstackrealign -I../../../projects/ -I../../../include/ STK_CategoricalParameters.cpp -c -o ../../../bin/STK_CategoricalParameters.o /bin/sh: line 1: /x86_64-w64-mingw32.static.posix/bin/g++: Bad address make[2]: *** [makefile:54: ../../../bin/STK_CategoricalParameters.o] Error 126 RTools uses Cygwin features to emulate the presence of certain virtual paths; /x86_64-w64-mingw32.static.posix/bin/g++ actually exists and is transparently mapped to d:/rtools43/x86_64-w64-mingw32.static.posix/bin/g++.exe: User@WINMACHINE MSYS ~ $ /x86_64-w64-mingw32.static.posix/bin/g++ --version g++.exe (GCC) 12.2.0 The "Bad address" here means that /bin/sh got an EFAULT while trying to launch g++.exe: https://stat.ethz.ch/pipermail/r-package-devel/2023q4/010223.html Unless there is something extremely weird in the command line arguments returned by Rscript -e "rtkore:::CxxFlags()" that causes the process to fail to launch (in my opinion, very unlikely, but can you print them from your compilation process just in case?), I would be looking for problems elsewhere. In particular, the problem cannot be in having rtkore installed that is one version too old, because you only changed Makevars in that version, and your package MixAll doesn't use the Makevars from a different source package. __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] Does dependencies up to date on the pretest CRAN infrastructure
Hello Duncan, Yes, you're right, I'll do that ! Serge Le 12/01/2024 à 19:47, Duncan Murdoch a écrit : I don't know if you can find out which rtkore version was installed, but your package should work with any rtkore version if you haven't declared a dependency on a particular version. So the simplest thing is just to declare that you depend on "rtkore (>= x.y.z)" where x.y.z has the recent fix. Duncan Murdoch On 12/01/2024 1:09 p.m., Serge wrote: I'm the mainteneur of the package MixAll. This package has a dependency to the package rtkore (whom I'm the mainteneur too). I updated the package rtkore one month ago, fixing a compilation problem on windows devel platform. MixAll has a dependency to rtkore. Thus, I suspect that the error reported below is due to the presence of the old version of rtkore on the pretest infrastructure of the CRAN. My question: is-it possible to know what is the version of rtkore installed on this pretest platform ? (and the https://win-builder.r-project.org/ site too, as I get the same error on this site). Il would certainly save me many tries, my suspicion should be true. Thanks, Serge Dear maintainer, package MixAll_1.5.4.tar.gz does not pass the incoming checks automatically, please see the following pre-tests: Windows: <https://win-builder.r-project.org/incoming_pretest/MixAll_1.5.4_20240108_094228/Windows/00check.log> Status: 1 ERROR Debian: <https://win-builder.r-project.org/incoming_pretest/MixAll_1.5.4_20240108_094228/Debian/00check.log> Status: 1 NOTE Last released version's CRAN status: OK: 1, NOTE: 8, WARNING: 2, ERROR: 1 See: <https://CRAN.R-project.org/web/checks/check_results_MixAll.html> CRAN Web: <https://cran.r-project.org/package=MixAll> Please fix all problems and resubmit a fixed version via the webform. If you are not sure how to fix the problems shown, please ask for help on the R-package-devel mailing list: > <https://stat.ethz.ch/mailman/listinfo/r-package-devel> If you are fairly certain the rejection is a false positive, please reply-all to this message and explain. More details are given in the directory: > <https://win-builder.r-project.org/incoming_pretest/MixAll_1.5.4_20240108_094228/> The files will be removed after roughly 7 days. __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] Does dependencies up to date on the pretest CRAN infrastructure
Hello Ivan,
Here the output of Cxxflags on my local computer
> rtkore::CppFlags()
-DIS_RTKPP_LIB -DSTKUSELAPACK
> rtkore::CxxFlags()
-I/home/iovleff/R/x86_64-pc-linux-gnu-library/4.3/rtkore/include
-I/home/iovleff/R/x86_64-pc-linux-gnu-library/4.3/rtkore/projects
and here the code of the functions used internally by CxxFlags() (cpp11 is
FALSE by default)
# Provide compiler flags -- i.e. -I/path/to/RTKpp.h
# @keywords internal
.rtkoreCxxFlags <- function(cpp11)
{
path1 <- .rtkore.system.file( "include" )
path2 <- .rtkore.system.file( "projects" )
if (.Platform$OS.type=="windows")
{
path1 <- .asBuildPath(path1);
path2 <- .asBuildPath(path2);
}
paste("-I", path1, " -I", path2, if (cpp11) " -std=c++11 " else "", sep="")
}
###
# Adapted from Rcpp package
###
# @rdname rtkoreFlags
# @keywords internal
.asBuildPath <- function(path)
{
if (.Platform$OS.type == "windows")
{
path <- normalizePath(path)
if (grepl(' ', path, fixed=TRUE))
path <- utils::shortPathName(path)
path <- gsub("", "/", path)
}
return(path)
}
Le 12/01/2024 à 20:14, Ivan Krylov a écrit :
В Fri, 12 Jan 2024 19:09:29 +0100
Serge пишет:
I updated the package rtkore one month ago, fixing a compilation
problem on windows devel platform.
MixAll has a dependency to rtkore. Thus, I suspect that the error
reported below is due to the presence of the old version of rtkore on
the pretest infrastructure of the CRAN.
<https://win-builder.r-project.org/incoming_pretest/MixAll_1.5.4_20240108_094228/Windows/00install.out>:
/usr/bin/make -C projects/Clustering/src/
make[2]: Entering directory
'/d/temp/RtmpYJkDTJ/R.INSTALL316dc7c0f48e6/MixAll/inst/projects/Clustering/src'
g++ -std=gnu++17 -I"D:/RCompile/recent/R/include" -DNDEBUG `D:/RCompile/recent/R/bin/Rscript -e
"rtkore:::CppFlags()"` -I'D:/RCompile/CRANpkg/lib/4.4/Rcpp/include'
-I'D:/RCompile/CRANpkg/lib/4.4/rtkore/include' -I"d:/rtools43/x86_64-w64-mingw32.static.posix/include"
`D:/RCompile/recent/R/bin/Rscript -e "rtkore:::CxxFlags()"` -I../inst/projects/ -I../inst/include/ -fopenmp
-pedantic -O2 -Wall -mfpmath=sse -msse2 -mstackrealign -I../../../projects/ -I../../../include/
STK_CategoricalParameters.cpp -c -o ../../../bin/STK_CategoricalParameters.o
/bin/sh: line 1: /x86_64-w64-mingw32.static.posix/bin/g++: Bad address
make[2]: *** [makefile:54: ../../../bin/STK_CategoricalParameters.o] Error 126
RTools uses Cygwin features to emulate the presence of certain virtual
paths; /x86_64-w64-mingw32.static.posix/bin/g++ actually exists and is
transparently mapped to
d:/rtools43/x86_64-w64-mingw32.static.posix/bin/g++.exe:
User@WINMACHINE MSYS ~
$ /x86_64-w64-mingw32.static.posix/bin/g++ --version
g++.exe (GCC) 12.2.0
The "Bad address" here means that /bin/sh got an EFAULT while trying to
launch g++.exe:
https://stat.ethz.ch/pipermail/r-package-devel/2023q4/010223.html
Unless there is something extremely weird in the command line arguments
returned by Rscript -e "rtkore:::CxxFlags()" that causes the process to
fail to launch (in my opinion, very unlikely, but can you print them
from your compilation process just in case?), I would be looking for
problems elsewhere.
In particular, the problem cannot be in having rtkore installed that is
one version too old, because you only changed Makevars in that version,
and your package MixAll doesn't use the Makevars from a different
source package.
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
[R-pkg-devel] Does dependencies up to date on the pretest CRAN infrastructure
I'm the mainteneur of the package MixAll. This package has a dependency to the package rtkore (whom I'm the mainteneur too). I updated the package rtkore one month ago, fixing a compilation problem on windows devel platform. MixAll has a dependency to rtkore. Thus, I suspect that the error reported below is due to the presence of the old version of rtkore on the pretest infrastructure of the CRAN. My question: is-it possible to know what is the version of rtkore installed on this pretest platform ? (and the https://win-builder.r-project.org/ site too, as I get the same error on this site). Il would certainly save me many tries, my suspicion should be true. Thanks, Serge Dear maintainer, package MixAll_1.5.4.tar.gz does not pass the incoming checks automatically, please see the following pre-tests: Windows: <https://win-builder.r-project.org/incoming_pretest/MixAll_1.5.4_20240108_094228/Windows/00check.log> Status: 1 ERROR Debian: <https://win-builder.r-project.org/incoming_pretest/MixAll_1.5.4_20240108_094228/Debian/00check.log> Status: 1 NOTE Last released version's CRAN status: OK: 1, NOTE: 8, WARNING: 2, ERROR: 1 See: <https://CRAN.R-project.org/web/checks/check_results_MixAll.html> CRAN Web: <https://cran.r-project.org/package=MixAll> Please fix all problems and resubmit a fixed version via the webform. If you are not sure how to fix the problems shown, please ask for help on the R-package-devel mailing list: > <https://stat.ethz.ch/mailman/listinfo/r-package-devel> If you are fairly certain the rejection is a false positive, please reply-all to this message and explain. More details are given in the directory: > <https://win-builder.r-project.org/incoming_pretest/MixAll_1.5.4_20240108_094228/> The files will be removed after roughly 7 days. __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] Getting 'Rscript: Bad address' error when CRAN build my package on windows platforms
It looks like the problem was coming from this line in the Makevars ## $(SHLIB) is the usual default target that is built automatically from all source ## files in this directory. pkglib is an additional target for the library ## that will be installed in inst/ and which users can link against. .PHONY: all all: $(SHLIB) Don't remember why I had these lines in the Makevars, the first release of the package is from 2015. A quick check on other packages on CRAN shows than it is (no more ?) not necessary. Serge Le 08/12/2023 à 12:24, Serge a écrit : > https://cran.r-project.org/web/packages/rtkore/ > > > and the Makevars in ./src/ is > > # > # Copyright (C) 2014-2015 Serge Iovleff, University Lille1, Inria > # > # This program is free software: you can redistribute it and/or modify > # it under the terms of the GNU General Public License as published by > # the Free Software Foundation, either version 3 of the License, or > # (at your option) any later version. > # > # This program is distributed in the hope that it will be useful, > # but WITHOUT ANY WARRANTY; without even the implied warranty of > # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the > # GNU General Public License for more details. > # > # You should have received a copy of the GNU General Public License > # along with this program. If not, see <http://www.gnu.org/licenses/>. > # > # Project: rtkore > # Created on: Feb 17, 2014 > # Authors: Serge IOVLEFF > #--- > ## define PKG_CPPFLAGS (preprocessor & includes) and PKG_CXXFLAGS (compiler > flags) > CXX_STD = CXX11 > > PKG_CXXFLAGS = -I'../inst/projects/' -I'../inst/include/' -DIS_RTKPP_LIB > -DSTKUSELAPACK > $(SHLIB_OPENMP_CXXFLAGS) > #PKG_CXXFLAGS = > PKG_LIBS = $(LAPACK_LIBS) $(BLAS_LIBS) $(FLIBS) $(SHLIB_OPENMP_CXXFLAGS) > > ## And export > export > > ## $(SHLIB) is the usual default target that is built automatically from all > source > ## files in this directory. pkglib is an additional target for the library > ## that will be installed in inst/ and which users can link against. > .PHONY: all > > all: $(SHLIB) > > Le 08/12/2023 à 11:12, Uwe Ligges a écrit : >> >> >> On 07.12.2023 19:29, Serge wrote: >>> Hello, >>> >>> I'm the maintener of the rtkore package and I'm experimenting an error >>> during the installation on >>> the |r-devel-windows-x86_64| and the |r-release-windows-x86_64| platform. >>> When trying to compile >>> I get >>> >>> |g++ -std=gnu++11 -I"D:/RCompile/recent/R-4.3.2/include" -DNDEBUG >>> -I../inst/projects/ >>> -I../inst/include/ -DIS_RTKPP_LIB -DSTKUSELAPACK >>> -I'D:/RCompile/CRANpkg/lib/4.3/Rcpp/include' >>> -I"d:/rtools43/x86_64-w64-mingw32.static.posix/include" -fopenmp -O2 -Wall >>> -mfpmath=sse -msse2 >>> -mstackrealign -c fastRand.cpp -o fastRand.o /bin/sh: line 1: >>> /x86_64-w64-mingw32.static.posix/bin/g++: Bad address | >>> >>> A search indicate that the problem is from the "D:" (not sure it is the >>> correct answer) >> >> Well, the missing d: or /d/ in the last line of your cited output. >> Which package is this? Then I could take a look into the sources. >> >> Best, >> Uwe Ligges >> >> >>> >>> In all case, I cannot modify these path as there given by the CRAN >>> mechanism of compilation. >>> >>> Can you give me some hints about the problem and how to solve it ? >>> >>> Thanks >>> >>> [[alternative HTML version deleted]] >>> >>> __ >>> R-package-devel@r-project.org mailing list >>> https://stat.ethz.ch/mailman/listinfo/r-package-devel > [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] Getting 'Rscript: Bad address' error when CRAN build my package on windows platforms
https://cran.r-project.org/web/packages/rtkore/ and the Makevars in ./src/ is # # Copyright (C) 2014-2015 Serge Iovleff, University Lille1, Inria # # This program is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program. If not, see <http://www.gnu.org/licenses/>. # # Project: rtkore # Created on: Feb 17, 2014 # Authors: Serge IOVLEFF #--- ## define PKG_CPPFLAGS (preprocessor & includes) and PKG_CXXFLAGS (compiler flags) CXX_STD = CXX11 PKG_CXXFLAGS = -I'../inst/projects/' -I'../inst/include/' -DIS_RTKPP_LIB -DSTKUSELAPACK $(SHLIB_OPENMP_CXXFLAGS) #PKG_CXXFLAGS = PKG_LIBS = $(LAPACK_LIBS) $(BLAS_LIBS) $(FLIBS) $(SHLIB_OPENMP_CXXFLAGS) ## And export export ## $(SHLIB) is the usual default target that is built automatically from all source ## files in this directory. pkglib is an additional target for the library ## that will be installed in inst/ and which users can link against. .PHONY: all all: $(SHLIB) Le 08/12/2023 à 11:12, Uwe Ligges a écrit : > > > On 07.12.2023 19:29, Serge wrote: >> Hello, >> >> I'm the maintener of the rtkore package and I'm experimenting an error >> during the installation on >> the |r-devel-windows-x86_64| and the |r-release-windows-x86_64| platform. >> When trying to compile >> I get >> >> |g++ -std=gnu++11 -I"D:/RCompile/recent/R-4.3.2/include" -DNDEBUG >> -I../inst/projects/ >> -I../inst/include/ -DIS_RTKPP_LIB -DSTKUSELAPACK >> -I'D:/RCompile/CRANpkg/lib/4.3/Rcpp/include' >> -I"d:/rtools43/x86_64-w64-mingw32.static.posix/include" -fopenmp -O2 -Wall >> -mfpmath=sse -msse2 >> -mstackrealign -c fastRand.cpp -o fastRand.o /bin/sh: line 1: >> /x86_64-w64-mingw32.static.posix/bin/g++: Bad address | >> >> A search indicate that the problem is from the "D:" (not sure it is the >> correct answer) > > Well, the missing d: or /d/ in the last line of your cited output. > Which package is this? Then I could take a look into the sources. > > Best, > Uwe Ligges > > >> >> In all case, I cannot modify these path as there given by the CRAN mechanism >> of compilation. >> >> Can you give me some hints about the problem and how to solve it ? >> >> Thanks >> >> [[alternative HTML version deleted]] >> >> __ >> R-package-devel@r-project.org mailing list >> https://stat.ethz.ch/mailman/listinfo/r-package-devel [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
[R-pkg-devel] Getting 'Rscript: Bad address' error when CRAN build my package on windows platforms
Hello, I'm the maintener of the rtkore package and I'm experimenting an error during the installation on the |r-devel-windows-x86_64| and the |r-release-windows-x86_64| platform. When trying to compile I get |g++ -std=gnu++11 -I"D:/RCompile/recent/R-4.3.2/include" -DNDEBUG -I../inst/projects/ -I../inst/include/ -DIS_RTKPP_LIB -DSTKUSELAPACK -I'D:/RCompile/CRANpkg/lib/4.3/Rcpp/include' -I"d:/rtools43/x86_64-w64-mingw32.static.posix/include" -fopenmp -O2 -Wall -mfpmath=sse -msse2 -mstackrealign -c fastRand.cpp -o fastRand.o /bin/sh: line 1: /x86_64-w64-mingw32.static.posix/bin/g++: Bad address | A search indicate that the problem is from the "D:" (not sure it is the correct answer) In all case, I cannot modify these path as there given by the CRAN mechanism of compilation. Can you give me some hints about the problem and how to solve it ? Thanks [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
