r one gets with pure
> luck :-)
>
Okay, Will do, thanks for the info!!
I just grabbed libtool-ml-20010411.tar.gz (the latest daily snapshot)
I couldn't seem to find a release version of libtool-ml, so Im guesing its
realtivly new, and still under devlopment. I was just wondering what
If you get to wondering why I go quiet for the next several days, you might
be interested to know that I will be mostly offline over the long Easter
weekend.
I plan to clear any patches left in the queue, test on the hosts I have
access to and release libtool-1.4 from HEAD upon my return. I w
> Try the multi-language branch in the CVS tree. Libtool 1.3.5 has
> > absolutely no support for C++ (other than whatever one gets with pure
> > luck :-)
> >
>
> Okay, Will do, thanks for the info!!
>
> I just grabbed libtool-ml-20010411.tar.gz (the latest dail
Does anyone know if there is a minimum version of
autoconf that needs to be used to build the latest
code from the HEAD branch?
I am running into a small problem when using our native
compiler because HAVE_MEMCPY is not being set (or even
checked for).
Could something other than autoconf be my p
Dan:
Libtool HEAD and MLB should work with autoconf-2.13,
as well as CVS versions. I haven't tested CVS versions
with HEAD, but I'd be suprised if they didn't work.
I doubt that autoconf is the problem, so why don't you post
some more details and a description of how to repeat
the problem.
Ro
On Wednesday 11 April 2001 11:03 pm, [EMAIL PROTECTED] wrote:
> I am running into a small problem when using our native
> compiler because HAVE_MEMCPY is not being set (or even
> checked for).
Do you have AC_CHECK_FUNCS(memcpy) in your configure.in?
Cheers,
Gary.
--
___ _
On Apr 6, 2001, Michael Matz <[EMAIL PROTECTED]> wrote:
> 2001-04-05 Michael Matz <[EMAIL PROTECTED]>
> * ltmain.in: recognize "C" as default --tag argument to resolve
> also ambiguities with that language.
Thanks. I've checked this in, except that I renamed the tag to CC,
for s
