This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: libtool - how to find/make it ?
On Sep 29, 2001, Toon Moene <toon@moene.indiv.nluug.nl> wrote:
>> sinclude(../libtool.m4)
>> dnl The lines below arrange for aclocal not to bring an installed
>> dnl libtool.m4 into aclocal.m4, while still arranging for automake to
>> dnl add a definition of LIBTOOL to Makefile.in.
>> ifelse(,,,[AC_SUBST(LIBTOOL)
>> AC_DEFUN([AM_PROG_LIBTOOL])
>> ])
> Hmmm, thanks for the idea, but it didn't work out.
> `/home/toon/compilers/snapshots/obj/i686-pc-linux-gnu/libf2c/libI77'
> make[3]: LIBTOOL@: Command not found
Hmm... I see each subdirectory of libf2c has its own configure
script, so each one should have similar magic (with the relative
sinclude pathname adjusted, naturally. But this would mean we
configure libtool once per sub-directory, which is far from optimal.
We might just set
LIBTOOL='$(SHELL) ../libtool'
AC_SUBST(LIBTOOL)
on sub-directories. On one hand, this would be good because it would
get `--enable-[shared/static]=libf2c' to affect all of the
sub-directories. But it would be bad in case libtool macros, at some
point, change the way the libtool script is generated. I.e., we'd be
violating the abstraction barrier, risking being bitten in the
future. I find it acceptable risk, but I have to defer the decision
to you, of course.
Another alternate would be to move all of the configury code in
sub-directories over to the top-level. I haven't analyzed whether
this would be feasible or desirable.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me