public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jerry DeLisle <jvdelisle@charter.net>
To: Damian Rouson <damian@sourceryinstitute.org>,
	gcc patches <gcc-patches@gcc.gnu.org>
Subject: [PATCH, contrib] Re: port contrib/download_prerequisites script to macOS
Date: Fri, 07 Apr 2017 01:04:00 -0000	[thread overview]
Message-ID: <fd790a09-29de-533c-67ab-02b7cea2751c@charter.net> (raw)
In-Reply-To: <etPan.58e44420.2d1bb7c0.14e0e@sourceryinstitute.org>

ping

On 04/04/2017 06:10 PM, Damian Rouson wrote:
> All,
> 
> The attached patch modifies the contrib/download_prerequisites script to work on macOS. 
> The revised script detects the operating system and adjusts the shasum and md5 commands 
> to their expected name and arguments on macOS.  The revised script also uses curl if 
> wget is not present.  macOS ships with curl but not wget.
> 
> Tested on macOS and Lubuntu and Fedora Linux distributions. 
> 
> Ok for trunk?
> 
> Damian
> 
> 
> 2017-04-05  Damian Rouson  <damian@sourceryinstitute.org>
> 
>         * download_prerequisites (md5_check): New function emulates Linux
>         'md5 --check' on macOS.  Modified script for macOS compatibility.
> 

  reply	other threads:[~2017-04-07  1:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-05  1:11 Damian Rouson
2017-04-07  1:04 ` Jerry DeLisle [this message]
2017-04-10 16:48 ` Mike Stump
     [not found]   ` <etPan.58ebd61c.3bd0724f.164e@sourceryinstitute.org>
2017-04-11 16:40     ` Jerry DeLisle
2017-04-12 22:03 ` Jeff Law
2017-04-13  0:40   ` Martin Sebor
2017-04-13  3:19     ` Jerry DeLisle
     [not found]   ` <etPan.58f001c5.14409c5f.c453@sourceryinstitute.org>
2017-04-13 23:29     ` Damian Rouson
2017-04-17 22:11       ` Martin Sebor

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=fd790a09-29de-533c-67ab-02b7cea2751c@charter.net \
    --to=jvdelisle@charter.net \
    --cc=damian@sourceryinstitute.org \
    --cc=gcc-patches@gcc.gnu.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).