This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFC] Update to current automake/autoconf/libtool versions.
- From: Alexandre Oliva <aoliva at redhat dot com>
- To: Klee Dienes <klee at apple dot com>
- Cc: Andrew Cagney <ac131313 at redhat dot com>, binutils at sources dot redhat dot com, gdb-patches at sources dot redhat dot com
- Date: 30 Dec 2002 17:41:09 -0200
- Subject: Re: [RFC] Update to current automake/autoconf/libtool versions.
- Organization: GCC Team, Red Hat
- References: <6D1408F4-0817-11D7-A7CE-00039396EEB8@apple.com>
Sorry I'm a bit late in following up. I don't follow these lists as
closely as GCC, and this should have been copied there, at least for
the parts that affects the top level, since those are shared.
On Dec 5, 2002, Klee Dienes <klee@apple.com> wrote:
> ltmain.sh (GNU libtool) 1.4.3
Can't do that. The copy we use is from a newer code base than the 1.4
branch of libtool. It's taken from a 1.5-to-be (multi-language)
branch from quite a while ago, back when the ltcf-*.sh scripts hadn't
been merged into libtool.m4.
> 2002-12-04 Klee Dienes <kdienes@apple.com>
> * .cvsignore: Add autom4te.cache.
Please don't. autom4te.cache is an aberration. It shouldn't be
created by default, and it shouldn't be left dangling there in the
source tree. I'd much rather have rules that remove it as soon as
configure is rebuilt.
> * acinclude.m4: Remove include of libtool.m4.
Can't let you do that, Dave. This causes us to use whatever
libtool.m4 happens to be in aclocal.m4's search path, which is very
likely not compatible with ltmain.sh from the top level. That's why
we use libtool.m4 from the top level and keep all the libtool files in
sync. I wouldn't mind updating to the libtool current CVS tree, which
would get us rid of a number of files in the top level, but this takes
a lot of testing on many different platforms.
> * configure.in: Use AC_PROG_LEX instead of AM_PROG_LEX.
> * configure: Pass --build=$host_alias to sub-makes if no other
> value is specified.
Huh? configure is generated from configure.in. Besides, it's wrong
in principle. --build is not to be the same as --host, it's the other
way round (even though autoconf 2.13 got it backwards). Gotta find
out why we depend on build being defaulted to host and fixing that
instead.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer