-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
| I believe this was an attempt at optimization: avoid testing for
| specific tools need only on one platform, unless libtool has been told
| that it is ON that platform. Oddly, you'd think that libtool would
| figure that out
Yaakov (Cygwin Ports) wrote:
One more patch will be required, namely, to define OBJDUMP where
necessary. I've rolled these two patches together, as attached.
Explanation:
The AC_LIBTOOL_WIN32_DLL macro was supposed to be used in packages which
built on Win32 platforms, in order to create DLLs.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
| Yaakov (Cygwin Ports) wrote:
|> AU_DEFUN([AC_PROG_LIBTOOL],
|> [LT_INIT
|> LT_OUTPUT
|> AC_DIAGNOSE([obsolete],
|> [$0: Remove this warning and the call to LT_OUTPUT if you do not need
|> libtool to exist before AC_OUTPUT.])
Yaakov (Cygwin Ports) wrote:
Charles Wilson wrote:
| I'm not so sure. I still think that calling LT_OUTPUT immediately after
| LT_INIT is not exactly equivalent to 1.5 behavior.
I think it is equivalent, seeing from a typical configure run with
libtool 1.5:
Looking at some of the other compatib
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
| I'm not so sure. I still think that calling LT_OUTPUT immediately after
| LT_INIT is not exactly equivalent to 1.5 behavior. I think that is too
| early...but I don't know how to force a non-local insertion of
| LT_OUTPUT, an
Yaakov (Cygwin Ports) wrote:
Charles Wilson wrote:
I'm now looking at 2.2, what I mean is instead of (in libtool.m4):
AU_ALIAS([AC_PROG_LIBTOOL], [LT_INIT])
AU_ALIAS([AM_PROG_LIBTOOL], [LT_INIT])
Do something like the following:
AU_DEFUN([AC_PROG_LIBTOOL], [
LT_INIT
LT_OUTPUT
])
AU_DEFUN([AM_P
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
| True. But that is NOT required. libtool-emit-time is simply a new
| (possible backwards-incompatible) behavior change of the new libtool --
| but one that hopefully impacts few clients.
I guess I'll be finding out exactly ho
Yaakov (Cygwin Ports) wrote:
Charles Wilson wrote:
| That should be taken up with the libtool maintainers. However, it has
[snip]
If I need to add LT_OUTPUT already, then I might as well switch entirely
to the LT_* macros.
True. But that is NOT required. libtool-emit-time is simply a new
(p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
| That should be taken up with the libtool maintainers. However, it has
| been their position, even in the libtool-1.4 and -1.5 days, that relying
| on that behavior was not recommended. Therefore they do not support it
| "di
Yaakov (Cygwin Ports) wrote:
*) Most packages still use a 1.5 libtool, if not older. Is LT_OUTPUT
the default if the old-style AC_PROG_LIBTOOL macro is called?
No, it is not.
If it's
not, it should be, as I know of a number of packages which rely on the
libtool script during configure.
Th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chuck,
I have yet to try libtool 2.2, but I'm sure that you have thoroughly
tested it. Could you clarify a few things:
*) Most packages still use a 1.5 libtool, if not older. Is LT_OUTPUT
the default if the old-style AC_PROG_LIBTOOL macro is cal
Brian Dessent wrote:
Angelo Graziosi wrote:
and if cygport depend on libtool1.5, how can the user who needs
libtool2.2 install it without uninstalling libtool1.5+cygport+...?
I think cygport should remove its requires: libtoolx.y from its
setup.hint. It currently lists that because the defa
12 matches
Mail list logo
