From: Andreas Schwab <schwab@suse.de>
To: "H. J. Lu" <hjl@lucon.org>
Cc: Paolo Bonzini <bonzini@gnu.org>,
Matthias Klose <doko@ubuntu.com>,
gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org
Subject: Re: PATCH: PR libjava/32078: Update libtool in classpath
Date: Tue, 29 May 2007 17:21:00 -0000 [thread overview]
Message-ID: <je3b1f4kys.fsf@sykes.suse.de> (raw)
In-Reply-To: <20070529155820.GA13758@lucon.org> (H. J. Lu's message of "Tue\, 29 May 2007 08\:58\:20 -0700")
"H. J. Lu" <hjl@lucon.org> writes:
> On Tue, May 29, 2007 at 05:44:37PM +0200, Andreas Schwab wrote:
>> Paolo Bonzini <bonzini@gnu.org> writes:
>>
>> >>>> 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.
>>
>> AC_CONFIG_AUX_DIR(../..) should work too.
>>
>
> Will it work with the standalone classpath?
That would be local change, of course.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2007-05-29 17:07 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-27 18:25 H. J. Lu
2007-05-27 18:53 ` H. J. Lu
[not found] ` <20070527182317.GA21785@lucon.org>
2007-05-29 10:25 ` Andrew Haley
2007-05-29 10:46 ` Andreas Schwab
2007-05-29 10:48 ` Andrew Haley
2007-05-29 13:10 ` Paolo Bonzini
2007-05-29 12:17 ` Matthias Klose
2007-05-29 13:43 ` H. J. Lu
2007-05-29 13:44 ` Paolo Bonzini
2007-05-29 13:47 ` H. J. Lu
2007-05-29 13:55 ` Paolo Bonzini
2007-05-29 14:25 ` Andrew Haley
2007-05-29 14:36 ` H. J. Lu
2007-05-29 14:40 ` Andrew Haley
2007-05-29 14:41 ` H. J. Lu
2007-05-29 14:43 ` Andrew Haley
2007-05-29 14:49 ` Andrew Haley
2007-05-29 15:09 ` Paolo Bonzini
2007-05-29 15:19 ` H. J. Lu
2007-05-29 15:19 ` Paolo Bonzini
2007-05-29 15:25 ` Andrew Haley
2007-05-29 15:36 ` H. J. Lu
2007-05-29 15:26 ` H. J. Lu
2007-05-29 15:44 ` Andrew Haley
2007-05-29 17:16 ` Maciej W. Rozycki
2007-05-29 14:46 ` Paolo Bonzini
2007-05-29 14:54 ` Andrew Haley
2007-05-29 14:59 ` Paolo Bonzini
2007-05-29 16:32 ` Andreas Schwab
2007-05-29 16:41 ` H. J. Lu
2007-05-29 17:21 ` Andreas Schwab [this message]
2007-05-29 17:36 ` H. J. Lu
2007-05-29 17:54 ` Andreas Schwab
2007-05-29 18:29 ` H. J. Lu
2007-05-29 18:35 ` Tom Tromey
2007-05-29 23:14 ` H. J. Lu
2007-05-30 8:22 ` Paolo Bonzini
2007-05-30 17:46 ` Tom Tromey
2007-05-30 18:03 ` H. J. Lu
2007-05-30 18:19 ` Tom Tromey
2007-05-31 9:37 ` Paolo Bonzini
2007-05-31 15:26 ` Tom Tromey
2007-05-30 20:01 ` Peter O'Gorman
2007-05-30 22:37 ` H. J. Lu
2007-05-29 17:05 Charles Wilson
2007-05-29 17:07 ` Charles Wilson
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=je3b1f4kys.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=bonzini@gnu.org \
--cc=doko@ubuntu.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl@lucon.org \
--cc=java-patches@gcc.gnu.org \
/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).