minisip trunk build error

Zach Welch zach-minisip at splitstring.com
Mon May 15 16:08:38 CEST 2006


Juha Heinanen wrote:
> zach,
> 
> would it be possible to check using configure or some other means that
> libtool is new enough and stop with error message if it is too old?

> i agree with you that it does not make sense to support buggy versions
> of other people's software, but it would save a lot of people's time if
> build process would know which versions of other software is needed for
> proper build of minisip.

Juha, This is an excellent suggestion; I added a check as r2507, and
this will probably annoy Cesc, Troy, or others to a state of frenzy....
;) As it happens, writing that patch made me realize that we can support
the older versions by moving the libtool version check into the m4 file
(or finding those variables that already get defined).

Cesc, the change I just suggested should be fairly easy to hack up for
testing purposes (see libmutil.m4); however, that solution would only
fix the "double .libs" bug. The libltdl install might still be broken in
that version as well, so r2507 still stands until you let me know the
status of that specific issue. If a newer version of libtool is required
to fix that, then 1.5.7 may not even be the necessary minimum.

Cheers,

Zach


More information about the Minisip-users mailing list