From: Alan Modra <amodra@gmail.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org,
golang-nuts@googlegroups.com
Subject: Re: libtool update for powerpc64le-linux
Date: Mon, 26 Aug 2013 03:45:00 -0000 [thread overview]
Message-ID: <20130826034511.GF3430@bubble.grove.modra.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1308232207380.12585@digraph.polyomino.org.uk>
On Fri, Aug 23, 2013 at 10:08:29PM +0000, Joseph S. Myers wrote:
> On Fri, 23 Aug 2013, Alan Modra wrote:
>
> > I'd like to import upstream libtool into gcc to support powerpc64le,
>
> Has the sysroot semantics issue been resolved in upstream libtool, or do
> you mean "import with 3334f7ed5851ef1e96b052f2984c4acdbf39e20c reverted"?
As far as I can tell, upstream libtool hasn't changed its sysroot
support since that patch went in. I wasn't even aware of the issue..
How did the gcc project get to the place where we aren't following our
own rules http://gcc.gnu.org/codingconventions.html regarding libtool?
We're supposed to get a patch reviewed upstream, applied, then import
the whole lot. From the top-level ChangeLog, that hasn't happened
since 2009-12-05! It must be a little disheartening to be a libtool
maintainer, when a major GNU project like gcc treats your work like
this.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2013-08-26 3:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 8:48 Alan Modra
2013-08-23 0:36 ` Alan Modra
2013-08-23 22:08 ` Joseph S. Myers
2013-08-26 3:45 ` Alan Modra [this message]
2013-09-16 7:17 ` Alan Modra
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=20130826034511.GF3430@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=golang-nuts@googlegroups.com \
--cc=java-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).