From: Damian Rouson <damian@sourceryinstitute.org>
To: fortran@gcc.gnu.org, Toon Moene <toon@moene.org>
Subject: Re: Patching the GCC build system to build MPICH and OpenCoarrays
Date: Wed, 04 Apr 2018 18:05:00 -0000 [thread overview]
Message-ID: <etPan.5ac513d8.382093d4.35eb@sourceryinstitute.org> (raw)
In-Reply-To: <1fbf07b7-d7bf-4418-6a04-939b55c09c7b@moene.org>
On April 4, 2018 at 3:09:39 AM, Toon Moene (toon@moene.org) wrote:
So "one compiler to compile them all".
I have encountered similar difficulties. This is another good to consider building everything at once.
Damian
prev parent reply other threads:[~2018-04-04 18:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-31 0:44 Damian Rouson
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 [this message]
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.5ac513d8.382093d4.35eb@sourceryinstitute.org \
--to=damian@sourceryinstitute.org \
--cc=fortran@gcc.gnu.org \
--cc=toon@moene.org \
/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).