I would Cc: the cygwin list, but it always bounces my messages...
On Fri, Sep 15, 2000 at 01:55:16PM +0300, Paul Sokolovsky wrote:
Hello Gary,
Hi!
Unfortunately, there's no online
archive of libtool-patches (why?), so I can't look there.
Wierd I added it to geocrawler *ages* ago, bt they
On Fri, Sep 15, 2000 at 08:08:31PM +0200, Bernard Dautrevaux wrote:
Hi all,
I'm trying to install CVS libtool in my environment and, after
several attempts, I have to request some help.
Oops, my bad. I hadn't tried a VPATH build since I removed ltconfig.
I checked a fix in earlier
Actually I was calling AC_LIBTOOL_CXX from configure.in,
the documentation seems to suggest that I should:
... To enable C++
support in libtool, use the `AC_LIBTOOL_CXX' macro in your
`configure.in' file.
I commented out that call, but it didn't help.
On Sep 16, 2000, Robert Boehne [EMAIL PROTECTED] wrote:
I'm no M4 guru, but it looks right to me. Any ideas?
It might be related with the behavioral differences of AC_REQUIRE
between autoconf 2.13 and CVS autoconf. It works for me, with
autoconf 2.13, but AC_REQUIRE is known to be broken in
Using CVS Automake, Autoconf, and multi-lingual libtool I see the
following message printed from configure:
checking whether a program can dlopen itself... cat: cannot open conftest.cc
no
Under Solaris 2.6.
I believe that the main-branch libtool prints the same message.
Bob
Hello,
An issue has recently been raised (by me) in the libtool mailing list
regarding the desirability of using the label "gnu-win32" in scripts
like libtool (and, I presume, configure).
I seem to recall that you have an objection to linking the name "GNU" to
something like "win32" because the
