minisip trunk build error
Cesc
cesc.santa at gmail.com
Sun May 14 20:38:58 CEST 2006
On 5/14/06, Zach Welch <zach-minisip at splitstring.com> wrote:
> Troy Cauble wrote:
> >
> > According to this thread, it was fixed 2 years ago in the
> > libtool 1.5 branch.
> >
> > http://lists.gnu.org/archive/html/libtool/2004-04/msg00146.html
> >
> > Peeking at the CVS ... my 1.5.6 version is *one commit* too old.
> > Anything later should fix it.
>
> 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".
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.
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
Regards,
Cesc
> Cheers,
>
> Zach
>
More information about the Minisip-users
mailing list