similar to: ices 2 and linking errors

I've tried everything I know how (and a lot I don't) to get ices to compile on this beige G3 ppc box. I've got the latest cvs of libshout and ices. Gentoo linux ppc 1.2-r1, from stage3 tarball. gcc 2.95.3 I've made sure that libshout points to libshout.so.2.0.2. Don't know what else to try. I've got the box here, and I've port-forwarded through my firewall to

I propose the following changes to the libshout API to support nonblocking I/O: New functions: int shout_set_nonblocking(shout_t *self, unsigned int nonblocking): Instructs libshout to use nonblocking I/O. Must be called before shout_open (no switching back and forth midstream at the moment). unsigned int shout_get_nonblocking(shout_t *self): self-explanatory. Changed functions:

Attached is a patch against shout-python-0.2 which does two trivial but very useful things (1) The function "get_connected" is exported so that shout-python becomes usable in nonblocking mode. In the current version of shout-python "open" raises an exception in nonblocking mode. (2) The global interpreter lock is released in the potentially blocking functions

On Sun, 25 Jan 2015 17:31:10 +0000 "Thomas B. R?cker" <thomas at ruecker.fi> wrote: > On 01/25/2015 04:22 PM, Marko Cupa? wrote: > > On Sun, 25 Jan 2015 15:06:45 +0000 > > "Thomas B. R?cker" <thomas at ruecker.fi> wrote: > > > >> On 01/25/2015 02:27 PM, Marko Cupa? wrote: > >>> Hi, > >>> > >>> I am

libshout 2.2.2 has just been released. From the NEWS file: * Handle Oggs that don't begin with zero granulepos. * Install header in correct location (broken in 2.2.1). * Theora memory leak fix. * Non-blocking shout_open was failing unnecessarily in the connect_pending state. * Cast some size_ts to ints for display purposes. You can find it at http://www.icecast.org/download.php when (if)

Hello I've configured the 'example.c' with the right SERVER, PORT, SHOUT FORMAT and all the required stuff, it works fine (the setup shout_set...() calls) but when reaching shout_open() it returns a socket error. $ ./example Error connecting: Socket error The configuration of the server and example.c is right, at least the server is up and running, and tried it with the

Hello... I have a doubt with the use of shout_send()... at low level, what should it send? the example reads from "stdin" and sends the read buffer with shout_send, but... where should fread() read from (behind the stdin)? I could think about something like this (for example) mpg123 "audio_file" ---> stdout --pipe-- stdin <--- libshout_application I include the

In the absence of any negative feedback (or positive, for that matter), I've decided to just go ahead and drop the new version of libshout, libshout 2.1. New features: * nonblocking I/O: call shout_set_nonblocking(1) before shout_open. If the socket is busy, your data will be queued until the next time libshout attempts a write. The current queue length in bytes is visible through

Hi List, i have a problem streaming mp3's to the icecast server via libshout-2.1. Everything works fine as long as i send ogg's to the icecast server. libshout as well as icecast do not report any errors. what might be the problem? my code looks like this: shout_init() shout_set_host(...) shout_set_password(...) shout_set_mount(...) shout_open() shout_set_format(...) while(

Hello. For various reasons I am writing my own source client. Most things seem to be working well. Connections work. shout_send() and shout_sync() seem to behave as expected. However, I find that if more than about 10-20 seconds passes between shout_send() calls then libshout crashes (takes my client down) during a subsequent shout_send(). Are there any rules about how often shout_send()

Hi I am using dovecot 2.0.9 on CentOS 6.4 The following error appears in the logs when users connect to the imap server using MACs. All other clients that I tested work fine. ###### BEGIN ERROR ###### Jan 5 18:04:25 mail dovecot: imap(jcf): Panic: file mailbox-list-maildir.c: line 133: unreached Jan 5 18:04:25 mail dovecot: imap(user): Error: Raw backtrace:

And more importantly (for me) - Can I ask question about Shout.pm? <p>Anders Jensen System devel. Cybercity.dk, OSS projektet ---- <erno> hm. I've lost a machine.. literally _lost_. it responds to ping, it works completely, I just can't figure out where in my apartment it is. Sig. provided by www.bash.org --- >8 ---- List archives: http://www.xiph.org/archives/

Hej folks, I''ve been trying to get a new machine up and running with the latest Xen for a while on a Slackware64 (current) machine. After installing Xen from source and building a new kernel with all xen options enabled I haven''t been able to get the machine to behave. The machine is a brand new dual opteron 6212 on a Supermicro H8DGi board with 64G ECC memory. Running a stock

Hej folks, I''ve been trying to get a new machine up and running with the latest Xen for a while on a Slackware64 (current) machine. After installing Xen from source and building a new kernel with all xen options enabled I haven''t been able to get the machine to behave. The machine is a brand new dual opteron 6212 on a Supermicro H8DGi board with 64G ECC memory. Running a stock

OS: OpenBSD 3.1 perl 5.6.1 libshout-1.0.9 Shout-1.0 Whatever I do, I cannot get Shout to see the libshout so. I'm pretty sure this is an ld problem but: bash-2.05# ldconfig -r | grep shout 72:-lshout.2.2 => /usr/local/lib/libshout.so.2.2 orry if I'm missing something simple...happy monday. --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage:

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

Here is the output. oldcomputer@ubuntu:~$ winecfg wine: creating configuration directory '/home/oldcomputer/.wine'... Xlib: extension "XFree86-DRI" missing on display ":0.0". wine: Unhandled illegal instruction at address 0x7e8ef4ef (thread 0009), starting debugger... Xlib: extension "XFree86-DRI" missing on display ":0.0". wine: Unhandled illegal

Hi Folks, I've facing an intermittent hang with a USB port which seems cam related: Event's that happen are: o USB modem (HUAWEI E220) plugged into PC ugen3.2: <HUA WEI> at usbus3 u3g0: <3G Modem> on usbus3 u3g0: Found 3 ports. umass0: <USB MASS STORAGE> on usbus3 umass0: SCSI over Bulk-Only; quirks = 0x0000 umass0:6:0:-1: Attached to scbus6 umass1: <USB

At 02:34 02-11-2002, you wrote: > >LD_RUN_PATH="/usr/lib" gcc -shared -L/usr/local/lib Shout.o -o > >blib/arch/auto/Shout/Shout.so -lshout > >/usr/bin/ld: cannot find -lshout >You need the actual (native) libshout, as well - then Shout.pm can >use it for the low-level streaming. Just install that where your >linker can find it, and it should work. I had

hi all for new users, finding asterisk info is unneccesary troublesome. the asterisk.org page has very little information about the product and using google for 'asterisk' is like using google for 'linux'. you get all too many hits that has nothing to do with the product. perhaps the asterisk.org page at least should point to voip-info.org? or perhaps it's time someone rewrote