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: Paolo Bonzini <bonzini at gnu dot org>
To: "H. J. Lu" <hjl at lucon dot org>
Cc: Matthias Klose <doko at ubuntu dot com>, gcc-patches at gcc dot gnu dot org, java-patches at gcc dot gnu dot org
Date: Tue, 29 May 2007 15:39:51 +0200
Subject: Re: PATCH: PR libjava/32078: Update libtool in classpath
References: <20070527182203.GA12846@lucon.org> <20070527182317.GA21785@lucon.org> <465C0461.2060605@ubuntu.com> <20070529131004.GB6442@lucon.org>

	PR libjava/32078
	* ltmain.sh: Update from gcc toplevel.
	* libtool.m4: New. Copied from from gcc toplevel.
	* ltsugar.m4: Likewise.
	* ltversion.m4: Likewise.
	* ltoptions.m4: Likewise.

why copy these? libjava/HACKING mentions to use -I flags to use them from the
toplevel directory.


I think ltmain.sh in classpath was used.  If it is true, will
-I use ltmain.sh from the toplevel directory?

No, you are right that you have to copy ltmain.sh at least.

Paolo

Follow-Ups:
- Re: PATCH: PR libjava/32078: Update libtool in classpath
  - From: H. J. Lu
- Re: PATCH: PR libjava/32078: Update libtool in classpath
  - From: Andreas Schwab

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: Matthias Klose
- Re: PATCH: PR libjava/32078: Update libtool in classpath
  - From: H. J. Lu

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