minisip trunk build error

[Zach Welch]

Cesc wrote:
> On 5/14/06, Zach Welch <zach-minisip at splitstring.com> wrote:
>> Great detective work; it looks like we require libtool >= 1.5.7. I have
>> just added a new document (README.deps in r2503) to explain this issue.
>>
>> Over time, we will expand that document to include additional tools, and
>> further quantify the minimum/tested versions (and their related quirks).
>>
> Hi Zach,
> 
> I hate to say it ... but i think that this is unacceptable. Minisip
> was perfectly buildable in such an environment (which is the default
> in Debian stable ... which is not going to change in the coming future
> and to which some of us like to stick due to its reliability), thus i
> don't think we can simply say "it won't compile there anymore, sorry".

Okay, so either use the patch that Troy pointed out, or use symlinks.
This is a bug in *libtool*, and *not* in our code. We absolutely should
not work around it; if anything, you need to complain to the Debian
libtool package maintainer and get that patch included. Right? Oh,
wait a sec; it is Debian's processes that are causing actual problem:
the "stable" tree is simply too old.

Besides, this is a development tool; the built packages should still run
on Debian stable, even if you have to upgrade libtool to do it.

> I think we can identify two different problems here:
> - libltdl
> - libtool and double .libs
> 
> The libltdl problem is related to the use of plug-ins ... the libltdl
> library used to be part of the libmutil folder, now we try to obtain
> it from an existing system folder. Either we go back to having it in
> the libmutil dir, or we fix the problem.

Again, this is a bug caused by your distribution failing to include a
correctly working libtool package; this is not a bug in minisip. In
fact, trying to go back is likely to break other use cases; there is
absolutely no way that fixing this is worth my time. If someone else
tries, I will be grossly annoyed if things are broken in the attempt.

Please do not blame my fixes to the codebase just because they have
exposed bugs in versions of the tools that are years out-of-date.
If anything, *that* is unacceptable.

> The libtool stuff ... ok, that we may not have so much control over. I
> still don't understand why it used to work and suddenly it started
> doing such a thing. Minisip from december 2005 works fine. Something
> changed ... we should figure it out. For the time being, at the very
> least, the build system should pop out an automatic alert telling the
> "ln -s . .libs" solution to solve the compilation problem ... people
> tend not to read the README files :D

Well, I'll give you one big clue: people want to use in-tree building
and not install things. That's just wrong, folks, but I have supported
your wishes as far as I can. If you want it to work better, you need to
use versions of the tools that do their job like they are supposed to.
Otherwise, you should not complain; there are clearly workarounds that
will allow you to get the job done.

There is not a real problem here.  Troy, what is your opinion on this?

Cheers,

Zach