From: <sisyphus1@optusnet.com.au>
To: "Ovais Khan" <okhan@tuskegee.edu>
Cc: <gcc-help@gcc.gnu.org>
Subject: Re: gfortran 7 compiler
Date: Fri, 16 Mar 2018 02:06:00 -0000 [thread overview]
Message-ID: <D8EADC5C68064ACEB399272FB4507A65@OwnerPC311012> (raw)
In-Reply-To: <BL0PR1901MB19876CD678D79285B5052745D8D70@BL0PR1901MB1987.namprd19.prod.outlook.com>
-----Original Message-----
From: Ovais Khan
Sent: Friday, March 16, 2018 12:36 PM
To: Jonathan Wakely
Cc: gcc-help@gcc.gnu.org
Subject: Re: gfortran 7 compiler
>Yes, I did tried that link but I did not get the gfortran compiler for
>windows, as I was getting earlier, e.g. in 2012 I have downloaded gfortran
>windows compiler very easily, but now I couldn't find any.
>Also, I checked the other link but couldn't find the gfortran compiler for
>windows.
I get the mingw-w64 compilers from the list at:
https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/7.2.0/
These compilers include gfortran.
I've not tried the installer that's on offer there, but under the "MinGW-W64
GCC-7.2.0" heading, you'll see 4 64-bit compilers (x86_64) offering a choice
of posix/win32 threads x a choice of sjlj/seh exception handling, and 4
32-bit compilers (i686) offering achoice of posix/win32 threads x a choice
of sjlj/dwarf exception handling.
The ones with posix threads and without sjlj exception handling are, I
believe, the most popular.
I have:
https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/7.2.0/threads-posix/seh/x86_64-7.2.0-release-posix-seh-rt_v5-rev0.7z
and
https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/7.2.0/threads-posix/dwarf/i686-7.2.0-release-posix-dwarf-rt_v5-rev0.7z
both of which are fine.
Cheers,
Rob
next prev parent reply other threads:[~2018-03-16 2:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 23:16 Ovais Khan
2018-03-15 23:18 ` Jonathan Wakely
2018-03-16 0:40 ` Ovais Khan
2018-03-16 0:42 ` Jonathan Wakely
2018-03-16 0:46 ` Jonathan Wakely
2018-03-16 1:36 ` Ovais Khan
2018-03-16 2:06 ` sisyphus1 [this message]
2018-03-16 4:58 ` J.W. Jagersma
2018-03-28 4:27 ` Ovais Khan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D8EADC5C68064ACEB399272FB4507A65@OwnerPC311012 \
--to=sisyphus1@optusnet.com.au \
--cc=gcc-help@gcc.gnu.org \
--cc=okhan@tuskegee.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).