This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: gfortran
- From: "Daniel Franke" <franke dot daniel at gmail dot com>
- To: "Paul, Brent S" <bpaul at alionscience dot com>
- Cc: fortran at gcc dot gnu dot org
- Date: Mon, 9 Jun 2008 21:50:51 +0200
- Subject: Re: gfortran
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=PZBQTZChj6MzbN0Oxwo5NLFyS6b0oDwp8jg9PL3gN5g=; b=QfICRHHjJKyOUJfppCeFq2TtEU/Z9e1PkYKtpiPLBLdsddva63s846jjfILM0KDxrD qfzUbkH8H20aKRzbQlPO0l5GlR0/VFq+LWh2kQiSKG22E3kk7s4Qczs6ezZ6d5UgEanw PtOFtUey1Dclu2lO2AKm94aVpS3Ayj2cTPLt8=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=lFiIIPnbWmB7M0V9A6BMHBwSF2GLTTtuGBLWqWuIOqfB1CTpMlqApANOK8pFhACSOv 4UsDDz//b0CPf6YRP3BOk10eIk9neToSLevLb9BA5JxkUtXknP2JPyQ/IkVdaLXNphfG mBqvmMd2rZUQb9dMoHiK7Z0pV4h1e8wI1jLPY=
- References: <EDF4E7B09CDA3C419C3948DD4B922D12D019EB@EMAIL2A.alionscience.com> <640ad44b0806091239t3b428e5fi2af3422986924a3@mail.gmail.com> <EDF4E7B09CDA3C419C3948DD4B922D12D46F14@EMAIL2A.alionscience.com>
2008/6/9 Paul, Brent S <bpaul@alionscience.com>:
> Daniel,
>
> $ gfortran -v
> Using built-in specs.
> Target: i686-pc-cygwin
> Configured with: ../gcc44/configure --prefix=/usr/local/gfortran
> --enable-languages=c,fortran --disable-bootstrap --enable-threads=posix
> --enable-sjlj-exceptions --enable-version-specific-runtime-libs
> --enable-nls --disable-libmudflap --disable-shared
> --disable-win32-registry --with-system-zlib --enable-checking=release
> --enable-werror --without-included-gettext --without-x --enable-libgomp
> Thread model: posix
> gcc version 4.4.0 20080517 (experimental) [trunk revision 135459] (GCC)
>
> I've also tried it without the "./" and there wasn't an executable
> created. I added the "./" because I was worried it was defaulting to
> some other directory.
Hm. Here I run FX' built as available from the wiki (20080514, Target:
i586-pc-mingw32) from cygwin. If this is supposed to work I can't
tell, however, it works for me. Or better, it works mostly, there are
some issues with absolute and relative paths names. That's why I
suggested to try without the './'.
Does gcc work with a simple .c file?