This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: PATCH: PR libjava/32078: Update libtool in classpath

From: Andrew Haley <aph-gcc at littlepinkcloud dot COM>
To: Andreas Schwab <schwab at suse dot de>
Cc: "H. J. Lu" <hjl at lucon dot org>, gcc-patches at gcc dot gnu dot org, java-patches at gcc dot gnu dot org, Classpath Patches <classpath-patches at gnu dot org>
Date: Tue, 29 May 2007 11:25:38 +0100
Subject: Re: PATCH: PR libjava/32078: Update libtool in classpath
References: <20070527182203.GA12846@lucon.org> <20070527182317.GA21785@lucon.org> <18011.63129.596623.418727@zebedee.pink> <jeabvo54u8.fsf@sykes.suse.de>

Andreas Schwab writes:
 > Andrew Haley <aph-gcc@littlepinkcloud.COM> writes:
 > 
 > > libtool in classpath is imported from upstream, so importing it here
 > > would be a fork.
 > 
 > The classpath copy in gcc has never used the imported libtool, but
 > rather a copy of the common gcc libtool.  See libjava/HACKING.

Ah, OK.  So, Classpath divergence isn't a problem, but divergence from
upstream libtool is.  

I'm not sure we should get into putting class files into autoconf
scripts, though.  I'm minded simply to accept HJ's patch rather than
do that.

Andrew.

Follow-Ups:
- Re: PATCH: PR libjava/32078: Update libtool in classpath
  - From: Paolo Bonzini

References:
- PATCH: PR libjava/32078: Update libtool in classpath
  - From: H. J. Lu
- Re: PATCH: PR libjava/32078: Update libtool in classpath
  - From: H. J. Lu
- Re: PATCH: PR libjava/32078: Update libtool in classpath
  - From: Andrew Haley
- Re: PATCH: PR libjava/32078: Update libtool in classpath
  - From: Andreas Schwab

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]