This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: libtools oddity, and --enable-targets=all pain
- From: Ian Lance Taylor <ian at airs dot com>
- To: Doug Evans <dje at transmeta dot com>
- Cc: binutils at sources dot redhat dot com
- Date: 29 Aug 2003 14:12:11 -0700
- Subject: Re: libtools oddity, and --enable-targets=all pain
- References: <200308292052.NAA22450@casey.transmeta.com>
Doug Evans <dje@transmeta.com> writes:
> Anyone know what the theory is behind the move-if-change dance here?
> With a --enable-targets=all build it's painfully slow.
Which part of it are you asking about? The comment in Makefile.am
says
# libtool will build .libs/libopcodes.a. We create libopcodes.a in
# the build directory so that we don't have to convert all the
# programs that use libopcodes.a simultaneously. This is a hack which
# should be removed if everything else starts using libtool. FIXME.
That is the reason we are copying libopcodes.a from opcodes/.libs to
opcodes/.
I wrote it using move-if-change to avoid forcing relinks just because
make dropped into the opcodes directory.
Currently the gdb Makefile expects to find opcodes/libopcodes.a.
Ideally gdb would start using libtool. Otherwise we could simply
change gdb to use opcodes/.libs/libopcodes.a. The `.libs' part is not
promised by libtool, but we can change it if libtool changes.
Ian