Dear Easybuilders, I have some problems with fortran linking. It looks that certain versions of fortran does not look for external block data in libraries. If one specifies the object file for the block data then the result is correct.
It seems that gfortran <= 4.8 works correctly, but gfortran >=4.9 not works correctly in some cases. bad results (all zeros in the answer): our site with foss/2015b, (GCC 4.9.3), foss/2016a (GCC 4.9.3), foss/2016b (GCC 5.4.0) , foss/2017a (GCC 6.3.0), foss/2017b (GCC 6.4.0), GCCcore 6.4.0, GCCcore 7.1.0 both SL 6 and CentOS 7) UGent foss/2018a (GCC 6.4.0), GCCcore 6.4.0 UCL (Louvain-le-neuve) HMEM GCC 6.3.0 UNamur HERCULES GCC 7.1.0 good results (non zero answers) our site with foss/2015a (GCC 4.9.2), and system compilers GCC 4.4.6 and GCC 4.8.5, singularity/docker ubuntu16.10 GCC 6.2.0, manual build GCC 6.4.0 with pure CentOS 7.4 deps. UBC (Vancouver, ComputeCanada) 5.4.0 UBC (Vancouver, ComputeCanada) 6.4.0 As far as I know, ComputeCanada does not use easybuild provided binutils (although I am not sure), the rest does (although I am not sure in case of UCL and UNamur), so first I thought this might be the problem, but it does not explain why the GCCcore 5+ versions does not work correctly. Then I installed GCC 6.4.0 manually, using purely CentOS 7.4. deps (GMP, MPFR and LIBMPC), and the the compiled program gives the right answer. I do not know how to proceed, and based on the results, I think that there is a problem with the EasyBuild GCC/GCCcore installation, but I do not how where it could be (I do not think that GMP, MPFR, ISL or LIBMPC is the problem, but I am not an expert) Any thoughts? (the sample program along with a compilation script is attached) Sincerely, Balazs
test.tar.gz
Description: test.tar.gz
