public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: Damian Rouson <damian@sourceryinstitute.org>
Cc: Richard Biener <richard.guenther@gmail.com>,
	gcc patches <gcc-patches@gcc.gnu.org>,
		gfortran <fortran@gcc.gnu.org>,
	Jerry DeLisle <jvdelisle@charter.net>
Subject: Re: [Patch] Edit contrib/ files to download gfortran prerequisites
Date: Sat, 21 Oct 2017 18:17:00 -0000	[thread overview]
Message-ID: <CAC1BbcRsWCQmuPO8+7xx7RE0+cNyxZqPDEA1F9wc0_YWiZdL_Q@mail.gmail.com> (raw)
In-Reply-To: <etPan.59ea941f.46020ae.1c2b@sourceryinstitute.org>

On 21 October 2017 at 02:26, Damian Rouson <damian@sourceryinstitute.org> wrote:
>
> Hi Richard,
>
> Attached is a revised patch that makes the downloading of Fortran prerequisites optional via a new --no-fortran flag that can be passed to contrib/download_prerequisites as requested in your reply below.
>
> As Jerry mentioned in his response, he has been working on edits to the top-level build machinery, but we need additional guidance to complete his work.  Given that there were no responses to his request for guidance and it’s not clear when that work will complete, I’m hoping this minor change can be approved independently so that this patch doesn’t suffer bit rot in the interim.
>
> Ok for trunk?

+ die "Invoking wget and curl in the 'download_prerequisites' script failed."

I suggest "Neither wget nor curl found, cannot download tarballs."

As an open-mpi user i question why this hardcodes MPICH, fwiw.

thanks,

  reply	other threads:[~2017-10-21 18:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-20 20:35 Damian Rouson
2017-09-21  7:40 ` Richard Biener
2017-10-21  0:26   ` Damian Rouson
2017-10-21 18:17     ` Bernhard Reutner-Fischer [this message]
2017-10-23 23:09       ` Damian Rouson
2017-10-27  2:27       ` Jerry DeLisle
2017-10-23 10:54     ` Richard Biener
2017-10-23 22:02       ` Damian Rouson
2017-10-24  8:26         ` Richard Biener
2017-09-22 22:24 Jerry DeLisle

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=CAC1BbcRsWCQmuPO8+7xx7RE0+cNyxZqPDEA1F9wc0_YWiZdL_Q@mail.gmail.com \
    --to=rep.dot.nop@gmail.com \
    --cc=damian@sourceryinstitute.org \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jvdelisle@charter.net \
    --cc=richard.guenther@gmail.com \
    /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).