Re: Packaging current lame CVS snapshot for Debian -- good or bad idea?
Fabian Greffrath <[email protected]>
| Newsgroups | gmane.comp.audio.mp3.lame |
|---|---|
| Message-ID | <[email protected]> |
Am Donnerstag, den 14.05.2015, 21:33 -0300 schrieb Rogério Brito: > Don't we have this problem on Debian also? I would have thought that we > would have had something like that, given that we compile tinfo separetely > from ncurses (or something like that). In Debian, lame is linked against libncurses which contains the initscr symbol that configure checks for. The libncurses library, in turn, is linked against libtinfo which contains the tgetent symbol that lame actually uses. Checking directly for the presence of the tgetent symbol in libtinfo first and then in libncurses thus makes sense, IMHO. - Fabian ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Lame-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lame-dev