Rtools43 is bleeding edge, and it is possible I was working with a stale
version.
On Tue, May 30, 2023 at 3:25 PM Dominick Samperi
wrote:
> Thanks for the feedback. I don't remember making such mods, and I am using
> the latest Rcpp, but to be safe I reinstalled Rtools43 and R 4.3.0 and the
> pr
Thanks for the feedback. I don't remember making such mods, and I am using
the latest Rcpp, but to be safe I reinstalled Rtools43 and R 4.3.0 and the
problem is resolved! Sorry about the false alarm.
Actually, I had two different installations of Rcpp, one under Program
Files\R\R-4.3.0, and
one un
f Rcpp?
From: Kevin Ushey
Sent: Tuesday, May 30, 2023 3:02 PM
To: Alexander Ilich
Cc: Dominick Samperi ; rcpp-devel
Subject: Re: [Rcpp-devel] Rcpp::sourceCpp Problem with R 4.3 update
I'm also not able to reproduce, but I see a different linker invocation:
g++ -shared -static-libgcc -o sour
I'm also not able to reproduce, but I see a different linker invocation:
g++ -shared -static-libgcc -o sourceCpp_3.dll tmp.def file43185fe94049.o
-LC:/rtools43/x86_64-w64-mingw32.static.posix/lib/x64
-LC:/rtools43/x86_64-w64-mingw32.static.posix/lib -LC:/R/R-43~1.0/bin/x64
-lR
In particular, your
What version of Rcpp are you using? With R 4.3 and Rcpp 1.0.10 I have no issues.
library(Rcpp)
Rcpp::sourceCpp(code='
#include
using namespace Rcpp;
// [[Rcpp::export()]]
SEXP cpptest(NumericVector v) {
return v;
}'
)
cpptest(1:5)
#> [1] 1 2 3 4 5
R.version
#>_
#
On 30 May 2023 at 14:27, Dominick Samperi wrote:
| Looks like the recent update to R 4.3 broke Rcpp::sourceCpp.
|
| Here is a simple example...
|
| library(Rcpp)
| Rcpp::sourceCpp(code='
| #include
| using namespace Rcpp;
| // [[Rcpp::export()]]
| SEXP cpptest(NumericVector v) {
|
