-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Salut Alexandre!
Alexandre Duret-Lutz wrote:
|>>>"Gary" == Gary V Vaughan <[EMAIL PROTECTED]> writes:
| Gary> FYI: I've made CVS libtoolize take its files from $aclocaldir again.
|
| Great! Thanks for doing this.
|
| Does it also handle the case where
On Wed, 2004-06-16 at 21:23 +0200, Alexandre Duret-Lutz wrote:
> >>> "Gary" == Gary V Vaughan <[EMAIL PROTECTED]> writes:
>
> [...]
>
> Gary> FYI: I've made CVS libtoolize take its files from $aclocaldir again.
>
> Great! Thanks for doing this.
>
> Does it also handle the case where AC_CONFIG
>>> "Gary" == Gary V Vaughan <[EMAIL PROTECTED]> writes:
[...]
Gary> FYI: I've made CVS libtoolize take its files from $aclocaldir again.
Great! Thanks for doing this.
Does it also handle the case where AC_CONFIG_MACRO_DIR isn't
used? libtoolize used to install all the m4 files in the
top-lev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexandre Duret-Lutz wrote:
| Changing libtoolize to install libtool.m4 locally is a great
| step, but it seems it would work as well if libtool.m4 was taken
| from /usr/share/aclocal/. Moving it away might be too harsh for
| users. AFAICT the real ad
>>> "Scott" == Scott James Remnant <[EMAIL PROTECTED]> writes:
Scott> On Thu, 2004-02-05 at 03:40, name wrote:
>> Why doesn't installation copy libtool.m4 to aclocal?
>>
Scott> Assuming you are talking about CVS HEAD (libtool 1.5a, future 1.6
On Thu, 2004-02-05 at 03:40, name wrote:
> Why doesn't installation copy libtool.m4 to aclocal?
>
Assuming you are talking about CVS HEAD (libtool 1.5a, future 1.6
release) this is because libtoolize now copies libtool.m4 from its own
data directory into your macro directory.
Why doesn't installation copy libtool.m4 to aclocal?
___
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool
There is no error message and no output and no file.
Works fine for one project, but not another.
the AC_CONFIG_AUX_DIR(config) works fine in one project,
but leaves the ltmain.sh, config.guess and config.sub
in the wrong directories for another. I don't remember
making any changes that would ca
On Mar 27, 2001, "Dan Harkless" <[EMAIL PROTECTED]> wrote:
> Everything is set up nicely so that the eventual link of the main
> executable will use libtool, but the test links done by configure
> _don't_ use it!
> Shouldn't AM_PROG_LIBTOOL cause configure to use libtool during all
> its test li
Howdy. Perhaps I'm missing something obvious, but it seems to me there's a
fundamental flaw in the libtool/autoconf integration (described as
"seamless" in the info docs).
I'm using libtool to allow my package to link with 3rd-party shared
libraries (that aren't in /usr/lib or the default share
10 matches
Mail list logo
