public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jerry DeLisle <jvdelisle@charter.net>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Damian Rouson <damian@sourceryinstitute.org>,
	Zaak Beekman <zbeekman@gmail.com>,
	gcc patches <gcc-patches@gcc.gnu.org>,
	gfortran <fortran@gcc.gnu.org>
Subject: Re: [Patch] Edit contrib/ files to download gfortran prerequisites
Date: Fri, 22 Sep 2017 22:24:00 -0000	[thread overview]
Message-ID: <52784c00-ea86-710e-3fb1-9e5ea90d37df@charter.net> (raw)

On Thu, 21 Sep 2017 09:40:49Richard Biener wrote:
> On Wed, Sep 20, 2017 at 10:35 PM, Damian Rouson
> <damian@sourceryinstitute.org> wrote:
> >> Attached is a patch that adds the downloading of gfortran prerequisites
> OpenCoarrays and MPICH in the contrib/download_prerequisites script.  The
> patch also provides a useful error message when neither wget or curl are
> available on the target platform.  I tested this patch with several choices
> for the command-line options on macOS (including --md5 and --sha512) and
> Ubuntu Linux (including --sha512).    A suggested ChangeLog entry is
>>
>>         * contrib/download_prerequisites: Download OpenCoarrays and MPICH.
>>         * contrib/prerequisites.sha5: Add sha512 message digests for
> OpenCoarrays and MPICH.
>>         * contrib/prerequisites.md5: Add md5 message digests for OpenCoarrays
> and MPICH.
>
>
> OK for trunk?  If so, I’ll ask Jerry to commit this.  I don’t have commit
> rights.

> Can you make this optional similar to graphite/isl?  Also I see no support in
> the toplevel build machinery to build/install the libs as part of GCC
> so how does that work in the end?

In the end gcc needs to know what to do and just do it just like mpfr and
libquadmath.

I started looking at Makefile.def and I am guessing this is where the changes
need to be made to enable gcc machinery to actually build the two packages.  I
am not knowledgeable enough to figure this out and I recently got a new job so
now am very time constrained as far as reverse engineering what is going on.

I did manage to add Gnu Build System autotools features to OpenCoarrays so we
could be closer to integrating this in. (./configure && make vs cmake)

We definitely need some guidance from someone regarding the changes required for
the top level gcc items.

Also we are getting some libtool related build failures with the OpenCoarrays on
Mac and some other platforms where we know gcc builds fine, so I suspect we need
to build a libtool script or something to ensure that it works everywhere. It
works fine on Fedora which is what I use (naturally).

So if anyone would step up to the plate and advise on the toplevel machinery it
would be greatly appreciated.

Regards,

Jerry

             reply	other threads:[~2017-09-22 22:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-22 22:24 Jerry DeLisle [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
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

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=52784c00-ea86-710e-3fb1-9e5ea90d37df@charter.net \
    --to=jvdelisle@charter.net \
    --cc=damian@sourceryinstitute.org \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.guenther@gmail.com \
    --cc=zbeekman@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).