minisip trunk build error

Zach Welch zach-minisip at splitstring.com
Mon May 15 17:34:10 CEST 2006


Troy Cauble wrote:
> Zach Welch wrote:
>  will allow you to get the job done.
> 
>>
>> There is not a real problem here.  Troy, what is your opinion on this?
> 
> 
> It'd be nice to make it work for as wide a range of tool versions
> as practical.  I already had to modify my pkg-config because Ubuntu
> uses version 0.19.  (You guys are using debian?  Doesn't that mean
> you're on the same version?)

Let's see if my memory can summarize: Cesc is using Debian, Mikael is
also using Win32, and Erik is also using OpenEmbedded; you are using
Ubuntu, Werner is using SuSE, and I am using Gentoo. That is all that I
an remember at the moment. Who did I omit? Where is our Red Hat rep?

> Also, all these build tools are inter-related in ways I don't want
> to think about, and forcing an upgrade in libtool might require
> something somewhere else.

Given the number of distributions we have, it is a troublesome prospect
no matter which way we try to cut it; however, we are not a stable
project, so I do not have much sympathy for Debian stable support.
By the time we reach 1.0, they may have made a new release. :)

> I, too, would like to *understand* how the problem manifests,
> but I don't have the time.

The problem arises due to an interaction with build.pl, which specifies
--with-* flags that trigger the m4 macros in libmutil.m4. In that file,
the AC_MINISIP_CHECK_WITH_ARG macro needs to be modified to check the
version of libtool and conditionally add the '.libs' extension only if
it is >= 1.5.7. I noticed a couple of other fixes that are needed.

Anyway, I think my other replies should cover this situation adequately.
Hang in there and I'll get things back to normal for 1.5.6 "tomorrow".

Cheers,

Zach


More information about the Minisip-users mailing list