This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: libtool - how to find/make it ?
Toon Moene <toon@moene.indiv.nluug.nl> writes:
|> Alexandre Oliva wrote:
|> >
|> > 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,
|>
|> Well, I don't think this is the problem - libf2c/Makefile.in isn't under
|> automake at all, presently.
|>
|> Perhaps I can just ask the questions I want to know an answer to,
|> instead of you having to guess where I'm heading :-):
|>
|> 1. Assuming libtool is not something installed on the system GCC is
|> built on - where does libstdc++-3 get it from ?
It's always part of the sources, built by the configure script. The
contents of the libtool.m4 macro file should be added to aclocal.m4
(either by copying or by using sinclude as above). The AC_PROG_LIBTOOL
macro should then do all what is required to create the libtool script in
the build directory. *Note Integrating libtool with your package:
(libtool)Integrating libtool.
Andreas.
--
Andreas Schwab "And now for something
Andreas.Schwab@suse.de completely different."
SuSE Labs, SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5