From: Paolo Bonzini <paolo.bonzini@lu.unisi.ch>
To: "Ralf Wildenhues" <Ralf.Wildenhues@gmx.de>,
"François-Xavier Coudert" <fxcoudert@gmail.com>,
"Steve Ellcey" <sje@cup.hp.com>,
dje@watson.ibm.com, bonzini@gnu.org,
"gcc-patches List" <gcc-patches@gcc.gnu.org>
Subject: Re: Patch to update libtool in GCC and binutils trees
Date: Mon, 02 Apr 2007 11:25:00 -0000 [thread overview]
Message-ID: <4610E809.9000108@lu.unisi.ch> (raw)
In-Reply-To: <20070402112101.GE11552@iam.uni-bonn.de>
Ralf Wildenhues wrote:
> * François-Xavier Coudert wrote on Fri, Mar 30, 2007 at 11:34:16AM CEST:
>> Also, when applying your patch and running autoconf in libjava (after
>> I did the aclocal && automake, as indicated in your previous mail) I
>> still get the following error:
>>
>> configure.ac:436: error: possibly undefined macro: AC_LIBLTDL_CONVENIENCE
>> If this token and others are legitimate, please use m4_pattern_allow.
>> See the Autoconf documentation.
>> autoreconf: /usr/bin/autoconf failed with exit status: 1
>>
>> So, that's occuring to me on both i686-pc-mingw32 and x86_64-linux,
>> it's weird that it's not occuring to anyone else. If it's relevant, I
>> only have a GCC tree, no src or other things.
This is because the new libtool does not include LIBLTDL macros in your
libtool.m4. You can either take them from HEAD libtool too, or move them
from the old libtool.m4 into a new libltdl.m4 file.
Paolo
next prev parent reply other threads:[~2007-04-02 11:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200703281744.l2SHin837088@makai.watson.ibm.com>
[not found] ` <200703282231.PAA13113@hpsje.cup.hp.com>
2007-03-30 10:24 ` François-Xavier Coudert
2007-03-30 11:56 ` François-Xavier Coudert
2007-04-02 11:21 ` Ralf Wildenhues
2007-04-02 11:25 ` Paolo Bonzini [this message]
2007-04-05 22:21 Steve Ellcey
2007-04-05 22:54 ` Alexandre Oliva
2007-04-06 16:24 ` Steve Ellcey
2007-04-06 16:59 ` Benjamin Kosnik
-- strict thread matches above, loose matches on Subject: below --
2007-03-30 4:16 Charles Wilson
2007-03-30 18:29 ` Steve Ellcey
2007-04-02 11:22 ` Ralf Wildenhues
2007-04-02 21:05 ` Steve Ellcey
2007-04-05 7:06 ` Alexandre Oliva
2007-04-02 11:19 ` Ralf Wildenhues
2007-03-23 17:12 Steve Ellcey
2007-03-26 16:58 ` Steve Ellcey
2007-03-26 18:01 ` Paolo Bonzini
2007-03-29 16:58 ` Steve Ellcey
2007-03-29 17:05 ` Andreas Schwab
2007-03-29 19:25 ` Steve Ellcey
2007-03-29 23:01 ` Steve Ellcey
2007-04-05 6:58 ` Alexandre Oliva
2007-03-30 7:24 ` Ben Elliston
2007-03-23 9:45 Paolo Bonzini
[not found] ` <200703231550.IAA20980@hpsje.cup.hp.com>
2007-03-23 16:37 ` François-Xavier Coudert
2007-03-23 0:10 FX Coudert
2007-03-22 21:48 Steve Ellcey
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=4610E809.9000108@lu.unisi.ch \
--to=paolo.bonzini@lu.unisi.ch \
--cc=Ralf.Wildenhues@gmx.de \
--cc=bonzini@gnu.org \
--cc=dje@watson.ibm.com \
--cc=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=sje@cup.hp.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).