On 06/16/2012 04:44 AM, Fabrício Zimmerer Murta wrote: > Alright, forwarding to the correct list. For some reason I thought automake@ > was the general list. Maybe too few coffee to my veins. > > I hope to see it soon on autoconf.
Thanks for the report, and for finally hitting the right list. > > From: Fabrício Zimmerer Murta > Sent: Saturday, June 16, 2012 4:15 AM > To: Automake List > Subject: Fw: BUG: AC_PROG_FC does not define GCF when compiler is gfortran This says GCF... > > Well, as stated, the fix is quite simple. > > And voila. Newly generated configure will say ‘yes’ or ‘’ to GFC according to > your compiler. > (had to re-generate autoconf.m4f with autom4te --language=autoconf --freeze > --output=autoconf.m4f) > > The patch would be as simple as: > --- fortran.m4 2012-05-26 23:17:39.464828247 -0300 > +++ fortran.m4_ 2012-06-16 03:58:07.099697178 -0300 > @@ -382,6 +382,11 @@ > _AC_ARG_VAR_LDFLAGS()dnl > _AC_ARG_VAR_LIBS()dnl > _AC_PROG_FC([$2], [$1]) > +if test $ac_compiler_gnu = yes; then > + GFC=yes ...while everything else in your patch says GFC. At any rate, this matches what we did in AC_PROG_CC in c.m4, so the general approach looks right. Unfortunately, you're a few months too late; this was already done in commit bd962acf in Oct 2011. Maybe the problem is that you aren't using autoconf 2.69. -- Eric Blake [email protected] +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
