This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: PR libgomp/41418: fix libgomp without fortran enabled
- From: Bernhard Reutner-Fischer <rep dot dot dot nop at gmail dot com>
- To: Ralf Wildenhues <Ralf dot Wildenhues at gmx dot de>
- Cc: gcc-patches at gcc dot gnu dot org, fortran at gcc dot gnu dot org
- Date: Sat, 17 Oct 2009 19:00:46 +0200
- Subject: Re: PR libgomp/41418: fix libgomp without fortran enabled
- References: <20091011110906.GB29288@gmx.de> <20091017060445.GD30957@gmx.de>
On Sat, Oct 17, 2009 at 08:04:46AM +0200, Ralf Wildenhues wrote:
>Ping <http://gcc.gnu.org/ml/gcc-patches/2009-10/msg00681.html>
>
>* Ralf Wildenhues wrote on Sun, Oct 11, 2009 at 01:09:06PM CEST:
>> OK for trunk? DaveK tested this on Cygwin without
>> --enable-languages=fortran, see
>> <http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41418#c19>
>> and I tested it on i686-pc-linux-gnu, with fortran enabled.
>[...]
>
>> Fix libgomp without --enable-languages=fortran.
>>
>> libgomp/ChangeLog:
>> 2009-10-11 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
>>
>> PR libgomp/41418
>> * configure.ac: Set FC to "no" if $GFORTRAN starts with "no"
>> or a hyphen (happens with fortran language disabled).
>> * configure: Regenerate.
>
>> --- a/libgomp/configure.ac
>> +++ b/libgomp/configure.ac
>> @@ -142,7 +142,12 @@ AM_MAINTAINER_MODE
>> # We need gfortran to compile parts of the library
>> # We can't use AC_PROG_FC because it expects a fully working gfortran.
>> #AC_PROG_FC(gfortran)
>> -FC="$GFORTRAN"
>> +case `echo $GFORTRAN` in
despite Jakub's ok, why spawn a subshell here?
case "x$GFORTRAN" in
x-* | xno* ) FC=no ;;
*) FC="$GFORTRAN ;;
esac
just curious..
>> + -* | no* )
>> + FC=no ;;
>> + *)
>> + FC="$GFORTRAN" ;;
>> +esac
>> AC_PROG_FC(gfortran)
>> FCFLAGS="$FCFLAGS -Wall"