Matt Denwood

Ah yes, if I set both: FCLIBS="/opt/gfortran/lib/gcc/aarch64-apple-darwin20.0/14.2.0/libgcc.a /opt/gfortran/lib/gcc/aarch64-apple-darwin20.0/14.2.0/libquadmath.a /opt/gfortran/lib/gcc/aarch64-apple-darwin20.0/14.2.0/libgfortran.a" And: FFLAGS="-static-libgfortran -static-libquadmath" Then this prevents -lquadmath being passed to the linker. The resulting binary has no runtime dependencies on gfortran/quadmath so that should be fine. I'll add all this to the macOS specific section of the installation...

Ah yes, if I set both: FCLIBS="/opt/gfortran/lib/gcc/aarch64-apple-darwin20.0/14.2.0/libgcc.a /opt/gfortran/lib/gcc/aarch64-apple-darwin20.0/14.2.0/libquadmath.a /opt/gfortran/lib/gcc/aarch64-apple-darwin20.0/14.2.0/libgfortran.a" And: FFLAGS="-static-libgfortran -static-libquadmath" Then this prevents -lquadmath being generated. The resulting binary has no runtime dependencies on gfortran/quadmath so that should be fine. I'll add all this to the macOS specific section of the installation guide,...

Sorry I didn't see this reply when I posted my message just now. I think allowing FCLIBS_USER to override the autoconf macro is a good solution - at least much better than my using find/sed to remove the -lquadmath flag from all Makefiles manually. I already know what the correct linker flags are; I just can't get them to propogate through the configure script correctly. For standard compilation this is obviously a non-issue - it is just for creating portable binaries - so I think an additional environmental...

Sorry I didn't see this reply when I posted my message just now. I think allowing FCLIBS_USER to override the autoconf macro is a good solution. I already know what the correct linker flags are; I just can't get them to propogate through the configure script correctly. For standard compilation this is obviously a non-issue - it is just for creating portable binaries - so I think an additional environmental variable that only I need to worry about is a good compromise. Having said that, if AC_FC_LIBRARY_LDFLAGS...

We should certainly try to avoid the libgfortran and libquadmath runtime dependencies, as these are not part of a standard macOS install (they are installed as part of the GNU gfortran binary that Simon provides via https://mac.r-project.org/tools/). However, I think I am now doing that, albeit using a hack... Using the following LDLAGS and LIBS: export LDFLAGS="-static-libgfortran" export LIBS="/opt/gfortran/lib/gcc/aarch64-apple-darwin20.0/14.2.0/libgcc.a /opt/gfortran/lib/gcc/aarch64-apple-darwin20.0/14.2.0/libquadmath.a"...

Update 2 The configure option --with-included-ltdl solves the libltdl dependency. There doesn't seem to be any neat way of preventing the -lquadmath flag being generated, but a manual find/sed step between configure and make resolves this (albeit in a hacky way). So the following works for static linkage to both gfortran (including libquadmath/libgcc) and openblas: export PATH="/opt/gfortran/bin/:$PATH" export LDFLAGS="-static-libgfortran" export LIBS="/opt/gfortran/lib/gcc/aarch64-apple-darwin20.0/14.2.0/libgcc.a...

Update With the following: export LDFLAGS="/opt/gfortran/lib/gcc/aarch64-apple-darwin20.0/14.2.0/libgfortran.a /opt/gfortran/lib/gcc/aarch64-apple-darwin20.0/14.2.0/libgcc.a /opt/gfortran/lib/gcc/aarch64-apple-darwin20.0/14.2.0/libquadmath.a -static-libgfortran" The build succeeds, and the libgfortran.dylib dependency is gone (although I do get clang++: warning: argument unused during compilation: '-static-libgfortran' [-Wunused-command-line-argument]). Unfortunately clang doesn't like -static-libgcc...

A small change in compilation speed between JAGS 4.2.0 and 4.3.2 could be expected due to the changes to the way in which JAGS reads the model definition, as described at https://martynplummer.wordpress.com/2016/09/14/you-can-always-make-it-faster/#more-822 However, you say "much faster", which implies a more dramatic difference. Can you provide a minimal reproducible example of a model that compiles much more quickly using JAGS 4.2.0 (preferably also including details of the timings under both versions,...