This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: libtool in binutils question
- From: Steve Ellcey <sje at cup dot hp dot com>
- To: aoliva at redhat dot com, macro at ds2 dot pg dot gda dot pl
- Cc: binutils at sources dot redhat dot com, gcc at gcc dot gnu dot org
- Date: Fri, 11 Jan 2002 15:35:25 -0800 (PST)
- Subject: Re: libtool in binutils question
> And then, there's the other issue: do we really want to require all
> developers of GCC and tools hosted in the src repo to be forced to
> switch to autoconf 2.5x? I'd rather not make that a requirement, but
> if a newer libtool forces that decision, we may have to eventually
> take that route.
OK, I went back to see why I needed autoconf 2.5 and I found I needed it
to bootstrap the latest libtool sources (CVS top-of-tree). I needed to
do that in order to create ltmain.sh which is created during the libtool
build process. Once I had ltmain.sh I copied it and libtool.m4 into the
binutils (and gcc) trees and tried running automake/autoconf with
autoconf 2.13. Unfortunately, it did not work because the new
libtool.m4 requires autoconf 2.50.
>From the libtool ChangeLog:
2001-08-01 Ossama Othman <ossama@doc.ece.uci.edu>
* libtool.m4 (AC_LIBTOOL_SETUP): Require Autoconf-2.50 via the
AC_PREREQ autoconf macro since the new libtool macros utilize
macros from that version of Autoconf.
Steve Ellcey
sje@cup.hp.com