minisip trunk build error

[Zach Welch]

Pssst.. you shouldn't trim the CC list.  ;)

Mikael Magnusson wrote:
> Zach Welch wrote:
> 
>> Juha Heinanen wrote:
>>
> 
>>
>> 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.
>>
> 
> I know two work-arounds for building libltdl in libmutil using libtool 
> version 1.5.6 (from Debian stable).
> 
> 1) Disable maintainer in libmutil, or

That's not a usable workaround, as we are talking about our maintainers.
(Anyone who uses SVN is a maintainer, in the eyes of the build system.)
Disabling maintainer mode makes it hard to work on the build system;
build.pl can make up for most of the rules that are disabled, but not as
efficiently. That is why it is enabled by default.

> 2) Copy libtool.m4 and ltdl.m4 to the libmutil directory. (This could be 
> done by bootstrap if it detects an old version.)

The immediate problem that I see with this is the potential portability
of the paths to those files; however, this can be solved with some new
extensions to build.pl. First, per-package callbacks; then, dist.conf
files can install a pre-bootstrap callback that copies those files.

So at this point, I have a complete solution for supporting 1.5.6 again,
but it will take me some time to implement it properly. Since I am
winding down for my work day, I want to wait to develop and commit the
necessary changes until after I sleep. In the meantime, please bear with
things as they are and use this second workaround.

Thanks,

Zach