shlib | portable functions for posix shell environments | Script Programming library

I have not come across this problem before, but the build file has been updated in attempt to accomodate multiple systems.

Can you try building fftw from the tarball?

So remove the ubuntu packages, then install fftw from the tarball, and let me know if you get the same error.

http://www.fftw.org/download.html

Best wishes,

It seems like the error was because of link time optimization. MinGW doesn't seem to like link time optimization, disabling it compiles wx just fine. I found the related information from here.

Finally I found the solution:

Since both system has the arch and OS. I cross copied the R compiled installations between them. The R which was compiled on the problematic system, but was run on the correct one gave the warnings below after the calling of the install.packages("renv", repos="https://cran.wu.ac.at/")

Check Build-options page in reference manual:

To change values in subprojects prepend the name of the subproject and a colon:

$ meson configure -Dsubproject:option=newvalue

Thus, try create new build dir with:

Try env ARCHFLAGS="-arch x86_64"

(that works for me for other Python-related tools, I don't use pyenv myself).

Rationale: modern macOS supports 2 architectures: intel (x86_64) and m1 (arm-something). Compiling for only one architecture is easier.

Yes, in ~/.R/Makevars for your compilations, in src/Makevars for all builds of the package. CRAN has views on which options are portable so you may not be able to ship with the option in src/Makevars.

Here is what I have:

There are a lot of things going on there we need to decompose.

First off, you managed to have SHLIB use your enumerated list of object files. Good! I recently had to the same and I used a OBJECTS list. I think you may get lucky if you stick the -fstack-protector into PKG_LIBS because the PKG_* variables are there for your expand on the defaults use (in the hidden Makefile controlled by R). Whereas ... LDFLAGS may just get ignored.

Otherwise, I would recommend to sample among the 4000+ CRAN packages with compiled code. Some will set similar things, the search with the 'CRAN' "org" at GitHub is crude but better than nuttin'. Good luck!

Edit: You could look at my (more complicated still) Makevars.win for RInside. I just grep'ed among all the repos I have here and I don't have a current example of anybody setting -fSOMETHING on Windows.

Edit 2: I do actually have a better example for your. Each and every RcppArmadillo package uses

For 99% of the use cases, one does not need to compile anything at all. Statistical workflows should be reproducible and have system level dependencies (curl and libz in your case). Then we can just use docker as a package manager and create a fresh pre-compiled R container:

Create a file called Dockerfile with the content

It is simpler to avoid using install.packages() when using an R environment managed by Conda, especially when the package involves compilation. Instead, prefer using Conda for installation. In this particular case, use