similar to: Problem Starting IceS

Displaying 20 results from an estimated 20000 matches similar to: "Problem Starting IceS"

2014 Nov 20
2
Problem Starting IceS
On Thu, 20 Nov 2014 19:38:31 +0200 (IST), you wrote: >On Thu, 20 Nov 2014, Steve Matzura wrote: > >> ices: error while loading shared libraries: libshout.so.3: cannot open >> shared object: no such file or directory > >As root, run: > >ldconfig > >Then try running it. Sorry, I forgot to report that I did that, too. Same error.
2014 Nov 25
1
Building IceS 0.4
I wound up finding and using an IceS augmentation called Centova Cast, which built, made and installed without a single error on my 64-bit system. It's IceS 0.4 with a couple additions. It's running now and behaving as it should, so this might be a solution for you as well. The install script is intense. It downloads everything you need, resolves dependencies, installs them, logs
2004 Aug 06
1
ices and libshout.so.1
> "./ices: error while loading shared libraries: libshout.so.1: cannot > open shared object file: No such file or directory" >>Is libshout installed? What I know I haven't installed it, is there a debian package of it so I can install or reinstall it mayne? >>Did you run ldconfig? When I do a ldconfig I get this back in return " ldconfig:
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
ices and libshout.so.1
Hello! I have compileed ices.0.2.2 for my debian system (the system is on a Mac PowerPC, so I use Debian-PPC) When I want to start Ices I get an error message saying this: "./ices: error while loading shared libraries: libshout.so.1: cannot open shared object file: No such file or directory" I start it with ./ices I checked and saw that I had the files but the maybe are in wrong
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
2005 Feb 02
1
ices-0.4 & libshout
hello members, i,ve installed ices-0.4 and libshout2 under suse linux 9.2. when i try to execute ices, got an error message: "ices: error while loading shared libraries: libshout.so.3: cannot open shared object file: No such file or directory" but i've compiled ices with libshout!? can some one help me? THANKS !!! Olaf -------------- next part -------------- An HTML attachment
2004 Aug 06
2
ices - unable to compile
Thanks...this seems to have gotten me over the compiling "hump". I get this when I run the ices binary: ./ices: error while loading shared libraries: libshout.so.1: cannot open shared object file: No such file or directory Are there some path settings that I need ? -----Original Message----- From: owner-icecast@xiph.org [mailto:owner-icecast@xiph.org]On Behalf Of Brendan Cully Sent:
2004 Aug 06
4
Stuttering stream
On Wed, 6 Feb 2002, Jack Moffitt wrote: > ices is built on libshout. libshout should have perfect timing and it > also detects and discards corrupt frames and supports VBR streams. It > is basically the _new_ version of shout. ices refuses to load. It whines about libmp3lame.so.0 being missing. I found the message in the archives that supposedly forces ices to compile with lame
2016 Apr 29
4
Trying to build ices-0.4 on ubuntu and "libshout not usable"
Hello: I hope someone can take a look at this and give me a little push to get me past this logjam. I've been running icecast + ices-0.4 + a perl application developed internally which runs an mp3 stream for a number of years. I am migrating my server from CentOS to ubuntu so I can upgrade to Perl 5.18 (so as to get clean unicode processing for another application.) I have installed
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
2019 Jul 10
2
Possible ICES/Icecast bug
Hi, I wonder if you can help. I am running Icecast 2.4.4, Ices 2.0.2 and libshout 2.4.3. There has been a recent upgrade to libshout and I notice that my previous ices configuration no longer works. In the ices log I get the error message: [2019-07-10 11:10:30] INFO ices-core/main IceS 2.0.2 started... [2019-07-10 11:10:30] INFO signals/signal_usr1_handler Metadata update requested [2019-07-10
2004 Aug 06
4
Problem with ices on OpenBSD 2.9 w/ Icecast 1.3.10
On Tuesday, 10 July 2001 at 14:10, Nick Ludlam wrote: > From: "Brendan Cully" <brendan@icecast.org> > > On Tuesday, 10 July 2001 at 03:21, Nick Ludlam wrote: > > > From: "Brendan Cully" <brendan@icecast.org> > > > > That handles the segfault, I don't know why the stream wouldn't be > > > > sent fast enough though...
2004 Aug 06
2
icecast 2 auth problem with (old?) ices, MuSe
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Michael and thanks for answer! On Tue, 13 Jan 2004, Michael Smith wrote: > This shouldn't be being passed to _check_pass_icy() at all - this isn't the > "icy" (shoutcast nasty ugly) protocol at all. We support that (icy) protocol > because it's widely used - but it's a horribly ugly hack to pretend that
2004 Dec 06
2
Re: ices, jack
On Mon, 06 Dec 2004 14:42:59 +0000, Karl Heyes wrote: > On Mon, 2004-12-06 at 09:31, adam wrote: >> alo >> >> i have seen some mention of an ices patch with support for jack...anyone >> know where i can get this? > > The latest is in SVN under http://svn.xiph.org/icecast/branches/kh and > tarballs are available in http://mediacast1.com/~karl. You will need
2014 Nov 24
0
Building IceS 0.4
Somehow I had the impressions that IceS 0.4 Either would not compile under a 64 bit OS Or was not compatible with a 64 bit OS In General I would Love to hear I Was Wrong.... That Ices 2 Sends ogg streams I can handle But that it Won't Read mp3 makes it Non-viable for me I can't afford to replace the extensive mp3 Library ----- Original Message ----- From: "Steve Matzura"
2004 Aug 06
2
Ices on Linux PPC
> > > > >>Also, will this live stream be Ogg or MP3? I need MP3. >> >> > >as mentioned before, ices2 will deal with ogg, mp3 can be dealt with by >ices 0.2.3 or some other source tool. > >karl > > Well, is ices 0.2.3 still being supported? Because I still can't get it to compile on the PPC even with new version of LAME and ogg
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
2
Can't compile ices kh static
Hello, I have oen trouble to compile ices kh 57 as a static executable. I built ogg, vorbis, libhshout with enable-static. ld.so.conf is up to date to find shared libs. When I compile ices non static, everything is ok. But when I add export LDFLAGS="-static" before calling configure for ices, then I get this error message: configure: error: Need libshout-kh release I'm using only
2015 Jul 06
2
Ices generates lots of email warnings
I can't say whether this is either an Ices or a CentovaCast issue, but there are certain programs that play perfectly normally but generate just piles of email about invalid sample rates or frames containing metadata that's not supported. Is there a way to turn these emails off? One of them recently was over four thousand lines long, which really shocked me, and it takes a lot to shock me.