Displaying 4 results from an estimated 4 matches for "get_lame_version".
2004 Aug 06
0
Ices-0.2.2, Lame 3.89b, FreeBSD 4.4-STABLE
...les\" -I../resolver -I../thread -I../libshout -I/usr/libdata/perl/5.00503/mach/CORE -I/usr/local/include/libxml2 -I/usr/local/include/libxml2/libxml -g -O2 -Wall -c reencode.c
reencode.c: In function `ices_reencode_initialize':
reencode.c:56: warning: implicit declaration of function `get_lame_version'
reencode.c: In function `ices_reencode_shutdown':
reencode.c:82: warning: implicit declaration of function `lame_close'
reencode.c: In function `ices_reencode_flush':
reencode.c:118: warning: implicit declaration of function `lame_encode_flush'
reencode.c: In function `reencode...
2004 Aug 06
2
Compiling with lame support
...the libmp3lame from /usr/lib instead of in /usr/local/lib
where I installed the latest version.
I used --with-lame-includes=/usr/local/include
--with-lame-libraries=/usr/local/lib.
However, I am still having some problems since my libmp3lame doesn't
have a lame_version(). I've changed to get_lame_version(). However,
lame_init_params() is crashing with a SEGV.
Is with lame-3.88 (beta) so maybe I'm trying to use a lame version
that's too new or has problems.
I also managed to get libxml2 (2.3.6) instead of libxml, but I linked
from xml2-config to xml-config) and it seems to work. I do get...
2004 Aug 06
3
icecast security
Jack Moffitt:
> > securityfocus mailing list (bugtraq) today (and several month before)
> > about a remote buffer overflow in icecast v1.3.10 (which seems to be a
>
> Point me to a url at bugtraq where I can read a description of the
> problem.
i've the today's email only in the web archive, here's a copy.
don't know if it's old news...
u.
2004 Aug 06
4
A few Newbie Questions on libwrap
On Tue, 17 Apr 2001, Andrew M. Wu wrote:
> Hello all,
>
> I have been having some trouble getting my Icecast server and IceS
> streamer up and running properly. I have successfully compiled both
> (Icecast 1.3.10 and IceS 0.0.1beta5) with libwrap and encrypt enabled.
>
> I can start up Icecast fine, with the following logged messages on
> startup:
>
> Icecast