similar to: libshout / ices configure test error, possible solution

Displaying 20 results from an estimated 10000 matches similar to: "libshout / ices configure test error, possible solution"

2004 Nov 17
2
ices-2.0.0 compile problems
Hi Running ./configure --prefix=/whatever I got stuck with checking for pkg-config... /usr/bin/pkg-config checking shout/shout.h usability... no checking shout/shout.h presence... no checking for shout/shout.h... no configure: error: must have libshout installed! Having edited configure line 20056 and changed shout/shout.h to /usr/include/shout.h , I run into the next problem:
2004 Aug 06
2
libshout 2.0 released
Hi all, I've just released libshout 2.0. This is the official release, not a beta. Thanks to all the testers who provided feedback during the beta period. http://icecast.org/files/libshout/libshout-2.0.tar.gz Libshout 2.0 adds support for icecast 2, Ogg streaming, and IPv6, as well as bug fixes relative to libshout 1. Ogg and Vorbis are now prerequisites. Changes since beta 3: * Minor
2004 Aug 06
2
libshout 2.0 released
Hi all, I've just released libshout 2.0. This is the official release, not a beta. Thanks to all the testers who provided feedback during the beta period. http://icecast.org/files/libshout/libshout-2.0.tar.gz Libshout 2.0 adds support for icecast 2, Ogg streaming, and IPv6, as well as bug fixes relative to libshout 1. Ogg and Vorbis are now prerequisites. Changes since beta 3: * Minor
2004 Aug 06
1
libshout headers
libshout 2.0 install its header file in /usr/include, whereas ices looks for /usr/include/shout/shout.h. Either one or the other should get fixed. [guillomovitch@klama guillomovitch]$ rpm -ql libshout3-devel | grep .h$ /usr/include/shout.h [guillomovitch@klama guillomovitch]$ rpm -ba rpm/SPECS/ices.spec [..] checking shout/shout.h usability... no checking shout/shout.h presence... no checking
2004 Nov 17
2
ices-2.0.0 compile problems
Jeremy Bierbach wrote: Hi Jeremy > It seems likely to me that you still have libshout 1.x installed. No, it's not that. # rpm -q libshout libshout-2.0-1.dag # rpm -q libshout-devel libshout-devel-2.0-1.dag It's the half-hard-coded shout/shout.h path in the source. Since libshout is installed by rpm in /usr/include, the path will never match. Even if
2004 Aug 06
1
libshout-perl compilation error
Hi - got this from both the CVS source and the tarball: (libshout compiled and installed cleanly) [root@hunter stream]# cd Shout-1.0 [root@hunter Shout-1.0]# perl Makefile.PL Checking if your kit is complete... Looks good Writing Makefile for Shout [root@hunter Shout-1.0]# make mkdir blib mkdir blib/lib mkdir blib/arch mkdir blib/arch/auto mkdir blib/arch/auto/Shout mkdir blib/lib/auto mkdir
2006 May 17
1
libshout includedir change
> Karl just pointed out to me that libshout is now installing its header > in $prefix/include/shout.h instead of $prefix/include/shout/shout.h. (Sorry for not replying directly, I'm not on the list and I can't figure out if gmane allows me to reply to a mail.) It's probably best to try and contact the committer first - It's possible few other people understand or care
2004 Aug 06
1
Patch to add User-Agent to libshout
Just a nifty thing to have for icecast server access logs... diff against CVS HEAD is attached. <p> Index: configure.in =================================================================== RCS file: /usr/local/cvsroot/libshout/configure.in,v retrieving revision 1.65 diff -u -r1.65 configure.in --- configure.in 13 Jul 2003 16:36:37 -0000 1.65 +++ configure.in 21 Jul 2003 04:20:22 -0000 @@
2004 Aug 06
1
compilling error ices-0.2.3.tar.gz
thnks for the clarfication. I downloaded libshout2 and ices-0.2 from cvs. I compiled libshout with out a problem but when i try and compile ices I get the following error: <p><p>checking whether to build shared libraries... yes checking whether to build static libraries... yes checking whether -lc should be explicitly linked in... no checking shout/shout.h usability... yes checking
2004 Aug 06
3
BUG: page-aligned data in libshout
I've spent three days tracking this bug down.. I have yet to find how to fix it in the code, tho I do have a workaround which proves the nature of the bug. Sorry for the somewhat-overkill nature of explaining this bug, but some people have been doubting it so I'm going to give the evidence nessesary to prove the nature of it. If you send page-aligned data to libshout (via shout_send) it
2004 Aug 06
3
BUG: page-aligned data in libshout
I've spent three days tracking this bug down.. I have yet to find how to fix it in the code, tho I do have a workaround which proves the nature of the bug. Sorry for the somewhat-overkill nature of explaining this bug, but some people have been doubting it so I'm going to give the evidence nessesary to prove the nature of it. If you send page-aligned data to libshout (via shout_send) it
2005 Feb 17
1
ices 2 and linking errors
I'm getting errors like; /tmp/ccJK5HgU.o(.text+0x426): In function `connect(shout*, std::basic_string<char, std::char_traits<char>, std::allocator<char> >)': : undefined reference to `shout_open' for each of the ices function calls. My gcc command looks like this; g++ -o myicestream -L/usr/lib/shout -lmysqlclient myicestream.cpp and libshout is in; find /usr -name
2004 Aug 06
4
icecast - libshout and ices
Hello, can anyone help me please? I have installed libxml2, libogg, libvorbis, and then i have cvsed and installed libshout (autogen.sh && make && make install). Then I cvsed ices and tried to run autogen.sh. It just quit with: checking for shout-config... /usr/local/bin/shout-config checking libshout settings Using libshout config in /usr/local/bin/shout-config checking
2004 Aug 06
2
IceS compiling problems
I have serious problems to compile IceS on a debian (woody), kernel 2.4.18. I have to say the configure script does not find anything... - I installed libshout and libshout-dev downloaded drom the icecast site. I have shout.h : 0:33 root@radiopi2 /usr/include/shout# ls shout.h Yet configure gives me this : ~/sources/ices-0.2.2% ./configure --with-libshout=/usr/include checking for
2004 Aug 06
1
compilling error ices-0.2.3 cvs
Brendan Cully wrote: >This particular error is because you used --with-libshout= instead of --with-libshout Is the above a typo. They look the same with the exception of the "=". I am new to linux so please be forgiving. I downloaded both ices and libshout. I tried to compile with "--with-shout-config=/etc/stream" but this returned the same result as in the previous email:
2004 Aug 06
3
perl libshout
Hi, I've just completed a conversion of the perl Shout-1.0 library to something that will talk to an icecast2 server. I'll be submitting the results for inclusion back to the icecast site. One thing is missing: proper metadata support. this feature has changed since icecast 1; previously it was a single string. now, it's a linked list of key/value pairs.
2004 Dec 07
1
Help: compiled libshout under win32
I want to use libshout under my win32 app (in Python) and download shout-python-1.0.tar.gz and libshout-2.0.tar.gz but I can not compile libshout into binary. It seems a unix-only project and there is no .dsp file for Visual Studio. Can anyone tell me how to compile libshout under win32 platform? Or send me a compiled version (a python binary dist will be better)? Thanks in advance.
2005 Jan 18
1
libshout error with pthread_mutex_init using Shout.pm
Any idea what might cause this error to happen on a FreeBSD 4.9 machine trying to use Shout.pm with perl 5.8.5 ? /usr/libexec/ld-elf.so.1: /usr/local/lib/libshout.so.3: Undefined symbol "pthread_mutex_init"
2014 Nov 21
2
Building IceS 0.4
I've been through this once before, and passing the proverbial camel through the eye of the proverbial needle seemed easier. $ ./configure ... configure:20721: checking for pkg-config configure:20739: found /usr/bin/pkg-config configure:20752: result: /usr/bin/pkg-config configure:20768: /usr/bin/pkg-config couldn't find libshout. Try adjusting PKG_CONFIG_PATH. configure:20774: checking
2004 Aug 06
2
Is the list alive?
At 13:44 31-10-2002, Michael Smith declared: >At 01:18 PM 31/10/2002 +0100, you wrote: > >And more importantly (for me) - Can I ask question about Shout.pm? >Yes. And yes, you can ask questions, but you should just do so - not >waste time asking if you can do so. This doesn't (either way) guarantee >anyone will be able to give you useful answers, but you should try