Date: Mon, 08 Feb 2021 23:51:44 +0000 From: bugzilla-noreply@freebsd.org To: fortran@FreeBSD.org Subject: [Bug 247485] math/lapack (and math/atlas) do not build with gcc10 Message-ID: <bug-247485-37611-Yz5NOeoFGS@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-247485-37611@https.bugs.freebsd.org/bugzilla/> References: <bug-247485-37611@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D247485 alt2600@icloud.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alt2600@icloud.com --- Comment #4 from alt2600@icloud.com --- Created attachment 222281 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D222281&action= =3Dedit path-Makefile Fixes build with GCC10(+?). gfortran10 has apparently went the way of strict type checking, which will cause problems with 30+ year old fortran librarie= s. I added -fallow-argument-mismatch to the F77FLAGS line in the do-build: loop = to make gfortran10 handle mismatches like and older fortran compiler would and atlas built. I attempted other methods like adding to EXTRAFLAGS but this seemed to break the C build. I'm guessing ATLAS checking the compiler flags causes issue when gcc10 spits back that this is a fortran flag not a C flag. Either way it builds now fine. not sure how lapack was fixed but it built f= ine during a system update to 12.2 I just completed. Given this has no maintain= er, I might consider taking it over. Just need to play a little to see how hard= it would be to get the newest support 3.10.3 version going a little bit, and w= hat lapacks it expects to see to optimize against. Not sure how far things have gone with upgrading lapack, lapacke, etc to later versions. I know those are tough given how many things require them. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-247485-37611-Yz5NOeoFGS>