> > Yeah, that's how it works. I realize this is less than good. Can you
> > suggest how it ought to work?
>
> I think the current behavior is fine, since it is indeed invalid to
> create a library or libtool archive out of no source files. However,
> we might output a warning (or even an erro
On 27 Nov 2000, Alexandre Oliva wrote:
> On Nov 25, 2000, Tom Tromey <[EMAIL PROTECTED]> wrote:
>
> >>> Do I have to use some macro in configure.in to fill $(LINK) with GNU ld?
> Alexandre> automake should define it to `$(LIBTOOL) $(CC/CXX)...'.
> Alexandre> Maybe it only does this when there is
On Nov 27, 2000, Steve Robbins <[EMAIL PROTECTED]> wrote:
> What I would like to do is:
> lib_LTLIBRARIES = libfoo.la
> libfoo_la_LIBADD = \
> $(top_builddir)/a/adummy.la \
> $(top_builddir)/b/bdummy.la \
> $(top_builddir)/c/cdummy.la \
>
Hi again,
nobody addressed the mail that I wrote a month ago, included again below,
it is still a problem for me however.
What is the right way of doing this? Or is indeed
something that is actually a problem with libtool?
On Thu, Oct 26, 2000 at 03:31:04PM +0200, Carlo Wood wrote:
> autoconf
I just updated to the latest CVS version of libtool and I noticed two
problems.
1) Even though I defined LT_NON_POSIX_NAMESPACE I still can't get lt_ptr_t
to work. After looking at the header file I discovered the really is
LT_FUBAR_NAMESPACE. Either the docs or the header files need to be
cha
On Tue, 28 Nov 2000, Kevin Atkinson wrote:
>
> I just updated to the latest CVS version of libtool and I noticed two
> problems.
>
> 1) Even though I defined LT_NON_POSIX_NAMESPACE I still can't get lt_ptr_t
> to work. After looking at the header file I discovered the really is
> LT_FUBAR_NAME
