Re: configuring libltdl

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexandre Duret-Lutz wrote: | On Tue, Nov 25, 2003 at 03:07:53PM +, Gary V. Vaughan wrote: | |>I thought you meant that Bruno had a macro that did AM_INIT_AUTOMAKE-a-like |>AC_SUBSTing for gettext's needs, and that another similar macro could do

Re: configuring libltdl

On Tue, Nov 25, 2003 at 03:35:25PM +, Gary V. Vaughan wrote: > If so, all we need is to add a call to AM_INIT_AUTOMAKE to > AC_LIB_LTDL. Hmmm, but then if a non-automake project calls > AC_LIB_LTDL, when they run autoreconf, it will run automake -a :-( Running automake in this case sounds s

Re: Defines dependent on static/dynamic build

On Tue, 25 Nov 2003, Gary V. Vaughan wrote: > | I seem to recall that libtool used to define something when compiling > | a shared library, but that this support was removed. Presumably this > | was because there was some other way to accomplish the same thing. > > I think you are thinking abou

Re: configuring libltdl

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bob Friesenhahn wrote: | On Tue, 25 Nov 2003, Alexandre Duret-Lutz wrote: | | |>On Tue, Nov 25, 2003 at 03:35:25PM +, Gary V. Vaughan wrote: |> |>>If so, all we need is to add a call to AM_INIT_AUTOMAKE to |>>AC_LIB_LTDL. Hmmm, but then if a non-au

Re: bootstrapping CVS libtool

On Wed, Nov 26, 2003 at 11:41:30AM +, Gary V. Vaughan wrote: I don't understand the above, but bootstraping libtool, I see: > ~ 1: remove $prefix/share/aclocal/l(ibtoo|td)l.m4 of old releases at > install > ~ time > ~ 2: keep copies of the latest versions only in $prefix/share/libtool/

avoiding C++, Fortran tags

hello libtool folks, i recently swiched to libtool 1.5 and now AC_PROG_LIBTOOL pulls in a horrendous amount of irrelevant checks for C++ and Fortran. to work around this, i have resorted to doing: aclocal echo 'AC_DEFUN([_LT_AC_TAGCONFIG],[])' >> aclocal.m4 probably it's better to call it a

Re: bootstrapping CVS libtool

On Wed, 2003-11-26 at 11:41, Gary V. Vaughan wrote: > Scott James Remnant wrote: > | This means if you use AC_FOO in m4/libtool.m4 then the first file that > | happens to AC_DEFUN that will get included, even though it's defined > | with m4_define in that same file. > > Gah! That has got to be a

Re: bootstrapping CVS libtool

On Wed, 26 Nov 2003, Patrick Welche wrote: > mkdir -p -- /usr/local/share/libtool/libltdl > cp: /usr/local/share/libtool/libltdl/./../m4/libtool.m4: No such file or directory > (so 2 doesn't seem to work automatically for me.. this is apart from having > to configure libtool twice so that the first

Re: configuring libltdl

On Wed, 26 Nov 2003, Gary V. Vaughan wrote: > > I don't really want to take on the burden of hand maintaining an enormous > generated Makefile.in, when maintaining a tiny Makefile.am and enhancing > automake a little to help with generation is possible. > > Why not try adding AC_REQUIRE([AM_INIT_AU

Re: avoiding C++, Fortran tags

On Wed, 2003-11-26 at 14:51, Thien-Thi Nguyen wrote: > i recently swiched to libtool 1.5 and now AC_PROG_LIBTOOL pulls in a > horrendous amount of irrelevant checks for C++ and Fortran. *snip* are > there plans to extend AC_PROG_LIBTOOL to specify which, if any, tags > are to be included/omitted?

Re: avoiding C++, Fortran tags

The ability to specify which tags to configure is already in libtool CVS and will be in the 1.6 release. The specification is done via AC_LIBTOOL_TAGS, so you could use AC_LIBTOOL_TAGS([]) to configure only the C tag. Bob On 26 Nov 2003, Thien-Thi Nguyen wrote: > hello libtool folks, > > i re

60-gary-remove-libltdl-subconfigury.patch [Was Re: configuring libltdl]

Bob Friesenhahn wrote: The issues I mention are primarily philosophical and religious. There is a subversive element of open source society that is willing to use Autoconf and Libtool, but not Automake. The FreeType and libJPEG projects come to mind. If AM_INIT_AUTOMAKE is used, then Automake mus

Tekbul internet Rehberi - iyi bayramlar.!

Tüm islam aleminin Ramazan bayrami kutlu olsun.! Beraber nice bayramlara ... TEKBUL.COM Administrator http://www.tekbul.com --- Tekbul internet Rehberi ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool

methinks libtool is too smart?

I'm working with a tree with libraries with a lot of cross dependencies (its currently in flux). It was originally a system with over a hundred objects, we're starting to use libaries now. all the libraries are static (I'm on solaris8 now). I need to link g++ -o foo foo.a -lcommon -lhw -

Re: configuring libltdl

Bob Friesenhahn <[EMAIL PROTECTED]> writes: > The issues I mention are primarily philosophical and religious. There > is a subversive element of open source society that is willing to use > Autoconf and Libtool, but not Automake. The FreeType and libJPEG > projects come to mind. Yup, I'm in tha

Re: 60-gary-remove-libltdl-subconfigury.patch [Was Re: configuring libltdl]

On Wed, 26 Nov 2003, Gary V. Vaughan wrote: > Bob Friesenhahn wrote: > > > > The issues I mention are primarily philosophical and religious. > > There is a subversive element of open source society that is willing > > to use Autoconf and Libtool, but not Automake. The FreeType and > > libJPEG pro

Re: methinks libtool is too smart?

On Wed, 26 Nov 2003, Marty Leisner wrote: > > I need to link > g++ -o foo foo.a -lcommon -lhw -lcommon -lhw > > So using an autoconf system, I have arule which looks like: > > libtool -n -mode=link g++ -o foo ../common/libCommon.la ../common/libCommon.la > and libtool translates this into: >

argv[0] is changed by temporary wrapper script

I'm a user of libtool. I used in a search engine Namazu . It has some test suites, and it was fine when I used libtool 1.4. However, libtool 1.5 causes error in the suites. The reason is treatment of argv[0] in temporary wrapper script. It was called like the following in

Re: Automake 1.7f uploaded (third beta for Automake 1.8)

>>> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes: adl> This is the third beta release of the next version of Automake (1.8). Sorry I messed with the URLs. The release is 1.7f, not 1.7e. Here are the corrected URL. ftp://alpha.gnu.org/gnu/automake/automake-1.7f.tar.gz ftp://alpha.gn