This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: libtool update for powerpc64le-linux
- From: Alan Modra <amodra at gmail dot com>
- To: "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: gcc-patches at gcc dot gnu dot org, java-patches at gcc dot gnu dot org, golang-nuts at googlegroups dot com
- Date: Mon, 26 Aug 2013 13:15:11 +0930
- Subject: Re: libtool update for powerpc64le-linux
- Authentication-results: sourceware.org; auth=none
- References: <20130816084805 dot GF4024 at bubble dot grove dot modra dot org> <20130823003554 dot GX3430 at bubble dot grove dot modra dot org> <Pine dot LNX dot 4 dot 64 dot 1308232207380 dot 12585 at digraph dot polyomino dot org dot 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