Re: valgrind & f951
Hi Tobias, > This is a false positive; you need to configure GCC with > |--enable-valgrind-annotations, see > https://gcc.gnu.org/install/configure.html thanks, that does the job after installing some valgrind-devel stuff. I apparently got stuck readings the description of --enable-checking, which also mentions valgrind, and then missed the relevant option. > If you don't bootstrap, be careful about compiler warnings as the > bootstrap compiler runs with -Werror in stage2 & 3. As long as I don't touch code outside fortran/libgfortran and watch new warnings, it is unlikely to break bootstrap for others. Thanks, Harald
Re: gfortran static linking under OS X (was: Re: )
On Sat, 20 Mar 2021, Iain Sandoe wrote: Daniel Feenberg wrote: On 3/19/21, Iain Sandoe wrote: On Fri, 19 Mar 2021, Tobias Burnus wrote: you should be able to work around this without changing the compiler or rebuilding it, %rename lib liborig *lib: -lquadmath -lm %(libgcc) %(liborig) ... I managed to install 10.2 and found that the error message goes away. No need to mess with the .spec file.A "static" binary can be produced with: gfortran taxsim.for -static-libgfortran -static-libgcc in version 10.2. however, I have only one Mac, so I can't be 100% sure the binary will port to another machine, but I am hopeful. Thank you all for your attention.. Daniel Feenberg NBER
