public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Joseph Myers <joseph@codesourcery.com>,
	"Bernhard M. Wiedemann" <bwiedemann@suse.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] ltmain.sh: Sort input file list
Date: Mon, 11 Jun 2018 18:47:00 -0000	[thread overview]
Message-ID: <fd112d9a-17d4-5b03-1710-1b2734fa0ef1@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1806111659580.19203@digraph.polyomino.org.uk>

On 06/11/2018 11:06 AM, Joseph Myers wrote:
> If we're not doing a general update from upstream libtool, I think we 
> should use the upstream ltmain.sh fix (libtool commit 
> 74c8993c178a1386ea5e2363a01d919738402f30, it looks like), or follow it as 
> close as possible, rather than having our own variant.
> 
Agreed.  My preference would be to get the various libtool, autoconf and
friends updated from the appropriate upstream projects.

jeff

  parent reply	other threads:[~2018-06-11 18:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-09 19:20 Bernhard M. Wiedemann
2018-06-11 17:06 ` Joseph Myers
2018-06-11 18:45   ` Bernhard M. Wiedemann
2018-06-11 18:47   ` Jeff Law [this message]
2018-06-12  1:50     ` Eric Gallager
2018-06-19  7:32     ` [PATCH] libtool: Sort output of 'find' to enable deterministic builds Bernhard M. Wiedemann
2018-06-25 11:39     ` Bernhard M. Wiedemann
2018-06-29  8:16       ` Richard Biener
2018-06-29 15:11         ` Jeff Law
2018-06-29 15:54           ` Jakub Jelinek
2018-06-29 16:40             ` Ian Lance Taylor
2018-06-29 17:34               ` Eric Gallager
2018-07-05 14:53           ` Bernhard M. Wiedemann
2018-07-05 19:14             ` Jeff Law

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=fd112d9a-17d4-5b03-1710-1b2734fa0ef1@redhat.com \
    --to=law@redhat.com \
    --cc=bwiedemann@suse.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.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).