From: Damian Rouson <damian@sourceryinstitute.org>
To: GCC Development <gcc@gcc.gnu.org>, gfortran <fortran@gcc.gnu.org>
Cc: "Daniel Celis Garza" <daniel.celisgarza@hmc.ox.ac.uk>,
"Jerry DeLisle" <jvdelisle@charter.net>,
"Filippone, Salvatore" <salvatore.filippone@cranfield.ac.uk>
Subject: Patching the GCC build system to build MPICH and OpenCoarrays
Date: Sat, 31 Mar 2018 00:44:00 -0000 [thread overview]
Message-ID: <etPan.5abed9f5.1a0112df.3c7@sourceryinstitute.org> (raw)
All,
Jerry DeLisle, Daniel Celis Garza, and I would greatly appreciate feedback on our approach to patching the GCC build system to build MPICH and OpenCoarrays after it builds gfortran (gfortran requires MPI and OpenCoarrays to support the parallel features of Fortran 2008 and Fortran 2018). A diff of our work relative to the GCC trunk is at http://bit.ly/2pQuzvS. Our steps so far include the following:
1. Jerry wrote an autotools build system for OpenCoarrays (on the OpenCoarrays issue-343-gnu-build branch.)
2. Jerry got MPICH and OpenCoarrays tar balls onto the GCC ftp server.
3. I modified GCC’s contrib/download_prerequisites script to download the tar balls.
4. Daniel edited GCC’s Makefile.def, config.ac, and Makefile.tpl to incorporate MPICH.
Our current issue is that the Makefile produced as follows doesn’t create the desired “mpi" directory:
git clone -b build-mpich https://github.com/sourceryinstitute/gcc
mkdir -p gcc/build
cd gcc/build
../configure --disable-bootstrap --enable-languages=fortran
whereupon "grep mpi Makefile” only returns comments and an echo statement. Ultimately, our desired sequence is to build gfortran, then build MPICH, and then build OpenCoarrays. All advice is welcome.
Damian
next reply other threads:[~2018-03-31 0:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-31 0:44 Damian Rouson [this message]
2018-04-03 11:36 ` Richard Biener
2018-04-04 6:24 ` Damian Rouson
2018-04-04 11:12 ` Richard Biener
2018-04-08 18:56 ` Damian Rouson
2018-04-09 11:43 ` Richard Biener
2018-04-04 13:09 ` Toon Moene
2018-04-04 18:05 ` Damian Rouson
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=etPan.5abed9f5.1a0112df.3c7@sourceryinstitute.org \
--to=damian@sourceryinstitute.org \
--cc=daniel.celisgarza@hmc.ox.ac.uk \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jvdelisle@charter.net \
--cc=salvatore.filippone@cranfield.ac.uk \
/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).