From: Toon Moene <toon@moene.org>
To: Thomas Koenig <tkoenig@netcologne.de>,
Damian Rouson <damian@sourceryinstitute.org>,
ams@codesourcery.com
Cc: Janne Blomqvist <blomqvist.janne@gmail.com>,
gcc patches <gcc-patches@gcc.gnu.org>,
gfortran <fortran@gcc.gnu.org>
Subject: Re: [PATCH 08/25] Fix co-array allocation
Date: Fri, 21 Sep 2018 07:33:00 -0000 [thread overview]
Message-ID: <62e8dc2f-68df-99e8-6231-da92a48d654c@moene.org> (raw)
In-Reply-To: <7bef0368-f709-642b-3bb4-14cb07aaba25@netcologne.de>
On 09/20/2018 10:01 PM, Thomas Koenig wrote:
> Hi Damian,
>
>> On a related note, two Sourcery Institute developers have attempted to
>> edit
>> the GCC build system to make the downloading and building of OpenCoarrays
>> automatically part of the gfortran build process. Neither developer
>> succeeded.
>
> We addressed integrating OpenCoarray into the gcc source tree at the
> recent Gcc summit during the gfortran BoF session.
>
> Feedback from people working for big Linux distributions was that they
> would prefer to package OpenCoarrays as a separate library.
> (They also mentioned it was quite hard to build.)
Well, Linux distributors have to fit the build of OpenCoarrays into
*their* build system, which might be just as complicated as we trying it
to force it into *gcc's* build system ...
For an individual, OpenCoarrays is not hard to build, and the web page
www.opencoarrays.org offers multiple solutions:
"Installation via package management is generally the easiest and most
reliable option. See below for the package-management installation
options for Linux, macOS, and FreeBSD. Alternatively, download and
build the latest OpenCoarrays release via the contained installation
scripts or with CMake."
I choose the cmake based one, because I already had cmake installed to
be able to build ECMWF's (ecmwf.int) eccodes package. It probably helped
that I also already had openmpi installed. From my command history:
1754 tar zxvf ~/Downloads/OpenCoarrays-2.2.0.tar.gz
1755 cd OpenCoarrays-2.2.0/
1756 ls
1757 less README.md
1758 cd ..
1759 mkdir opencoarrays-build
1760 cd opencoarrays-build
1761 (export FC=gfortran; export CC=gcc; cmake ../OpenCoarrays-2.2.0/
-DCMAKE_INSTALL_PREFIX=$HOME/opencoarrays)
1762 make
1763 make test
1764 make install
After that, it was a breeze to test my mock weather program
(moene.org/~toon/random-weather.f90), that I had built until then only
with -fcoarray=single.
--
Toon Moene - e-mail: toon@moene.org - phone: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
At home: http://moene.org/~toon/; weather: http://moene.org/~hirlam/
Progress of GNU Fortran: http://gcc.gnu.org/wiki/GFortran#news
next prev parent reply other threads:[~2018-09-21 7:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <024e798b9539b765a1259cfc9cb2f1dc480b24ca.1536144068.git.ams@codesourcery.com>
2018-09-05 16:54 ` Fwd: " Toon Moene
2018-09-05 17:02 ` Bernhard Reutner-Fischer
2018-09-05 18:07 ` Janne Blomqvist
2018-09-19 16:24 ` Andrew Stubbs
2018-09-19 21:18 ` Damian Rouson
2018-09-19 22:30 ` Andrew Stubbs
2018-09-19 23:09 ` Damian Rouson
2018-09-20 20:02 ` Thomas Koenig
2018-09-20 20:56 ` Damian Rouson
2018-09-21 7:33 ` Toon Moene [this message]
2018-09-23 11:40 ` Janne Blomqvist
2018-09-21 16:25 ` OpenCoarrays integration with gfortran Jerry DeLisle
2018-09-21 19:13 ` Janne Blomqvist
2018-09-21 19:37 ` Richard Biener
2018-09-21 20:17 ` Damian Rouson
2018-09-21 23:23 ` Jerry DeLisle
2018-09-23 9:47 ` Toon Moene
2018-09-23 16:48 ` Bernhard Reutner-Fischer
2018-09-23 19:17 ` Toon Moene
2018-09-23 20:19 ` Bernhard Reutner-Fischer
2018-09-24 10:58 ` Alastair McKinstry
2018-09-27 12:29 ` Richard Biener
2018-09-27 13:32 ` Jorge D'Elia
2018-09-20 15:56 ` [PATCH 08/25] Fix co-array allocation Janne Blomqvist
2018-09-20 16:23 ` Andrew Stubbs
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=62e8dc2f-68df-99e8-6231-da92a48d654c@moene.org \
--to=toon@moene.org \
--cc=ams@codesourcery.com \
--cc=blomqvist.janne@gmail.com \
--cc=damian@sourceryinstitute.org \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=tkoenig@netcologne.de \
/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).