similar to: make problems on libshout CVS.

Yep. That one was right on the nose. Sorry about that folks, I was using the simple "I'm going to the web cvs and downloading the tarball" instead of cvs -f -d :pserver:anoncvs@xiph.org:/usr/local/cvsroot login way of doing things Thanks for the fast reply. I am humbled. :) On Thu, Mar 13, 2003 at 07:11:44PM +1100, Michael Smith wrote: > On Thursday 13 March 2003 18:16, Mr.

----- Original Message ----- From: "Michael Smith" <msmith@xiph.org> To: <icecast-dev@xiph.org> Sent: Wednesday, June 04, 2003 3:47 PM Subject: Re: [icecast-dev] libshout2 compiling problems under FreeBSD? <p>> Whilst there may well be problems, there are no _known_ problems, and we > certainly won't be able to fix them unless you actually tell us what the

Hi, I've been trying to compile icecast 2. As yet no joy, but came across http://melmoth.dyndns.org/stream/doc this is indirectly linked from the icecast site...but i was getting really desperate when i thought i'd try my french - please link this useful english docu directly! But now... now i'm stuck. I'm following instructions in above mentioned docu to the letter... and

No, it's not his version of autoconf or automake. I had the same errors even with the latest versions available for my debian distribution. I only could help myself by using one of my precompiled binaries from a previous cvs snapshot. I haven't tried it with the current snapshot but I also don't know if there had been any update lately. Michael Smith wrote: >>all ok until

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

Package: src:blktap Version: 2.0.90-1 Severity: important Tags: sid jessie User: debian-gcc at lists.debian.org Usertags: ftbfs-gcc-4.8 The package fails to build in a test rebuild on at least amd64 with gcc-4.8/g++-4.8, but succeeds to build with gcc-4.7/g++-4.7. The severity of this report may be raised before the jessie release. tapdisk-logfile.c:166:23: error: argument to 'sizeof'

Package: src:blktap Version: 2.0.90-3 Severity: normal Tags: sid stretch User: debian-gcc at lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built

Okay, So remember that question I had last week about taking a bunch of relay servers and greping the status2.xsl file for the number of listeners? I coded it. I have to apologize right now, as its krufty, nasty, braindead code. But it works, and I'm rather proud that after being up as long as I have been up and drinking as much coffee, it works. It should be attached to this e-mail. I

I changed the libshout2 and thread module apis. This broke everything. If you are tracking CVS, make sure to update your libshout2 and the thread module. Ices2 and Icecast2 already uses these new changes, which were implemented as part of general cleanup and getting Solaris builds out of clean tarballs. If anyone is having build issues now, on linux or solaris, please let me know. jack. ---

Hi I''m trying to install fastcgi and I''ve downloaded the developers kit fromfastcgi.com I go through the instructions $ wget <a href="http://fastcgi.com/dist/fcgi-2.4.0.tar.gz">http://fastcgi.com/dist/fcgi-2.4.0.tar.gz</a> $ tar zxvf fcgi-2.4.0.tar.gz $ cd fcgi-2.4.0 $ ./configure $ makeMaking all in libfcgi but when it comes to making it it allways

I get an error when compiling libshout. it's the version from cvs, i checked it out a few minutes ago... make[2]: Entering directory `/opt/ices2/libshout/src/net' /bin/sh ../../libtool --mode=compile gcc -DPACKAGE=\"libshout\" -DVERSION=\"2.0\" -DHAVE_DLFCN_H=1 -DSTDC_HEADERS=1 -DHAVE_STDINT_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_C99_INTTYPES=1 -DHAVE_NANOSLEEP=1

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey all, did you happen to see this recent post to bugtraq? If so, I apologize. I haven't been keeping up with the archives since everything has been running so smoothly. ;) - --Stauf - -------- Original Message -------- Subject: IceCast up to v2.20 multiple vulnerabilities Date: 18 Mar 2005 22:31:14 -0000 From: Patrick

for am in automake-$AM_NEEDED automake$AM_NEEDED \ automake automake-1.7 automake-1.8 automake-1.9 automake-1.10; do This code makes it check for automake-1.7 (AM_NEEDED evaluates to 1.7), then automake (unversioned wrapper), then 1.7 (again), 1.8, 1.9 and then 1.10 1) Why the check is generally ascending? Isn't it better use the most recent version that is known to work instead of

Hi, I couldn't find anything about this subject from archive - are there known problems with compiling libshout2 under FreeBSD 5.1 or 4.8 (both are up to date). I downloaded libshout2 latest nightly snapshot and tried to compile it on 5.0 and then later on 4.8. Both failed (problems were mostly around sock.c, sock.h, resolver.c - redeclaring and syntax errors). Thinking that it might be a

To all CVS users of ices 0.x: I've just merged the ices-libshout_2 branch onto HEAD. Anyone using that branch should switch back to HEAD to continue to get the latest updates. This also means you now need the latest version of libshout2 from CVS in order to build ices from CVS. libshout2: :pserver:anoncvs@cvs.xiph.org:/usr/local/cvsroot libshout ices:

On Thursday 04 October 2007 04:27:47 you wrote: > Sir, you need to provide more information. What kind of errors? What > is not working? What exactly are you trying to do? What compiler are > you using? H IV0, we are using a lot of different cross-compiler (mainly based on GCC 3.4.x) When I tried to cross-compile FLAC for non-i386 platforms (such as ARM), I use use

Due to a minor reorganization of the CVS tree, cvs update of libshout will fail on the m4 directory. Either do a fresh checkout or remove your m4 directory and check out cvs.xiph.org:/usr/local/cvsroot m4 in its place. ices (0 and 2) and icecast may be going through the same process soon. I'll let you know when it happens. -b --- >8 ---- List archives: http://www.xiph.org/archives/

I recently compiled the drm and nouveau modules on Debian unstable. All went well until I had to insert the drm module, I recieved to following error: insmod: error inserting 'drm.ko': -1 Unknown symbol in module I have compiled the modules before and I have always gotten this same error. Here is the log of my build: debian:/home/michael/drm# ./autogen.sh --prefix=/usr && make

I have just made an attempt at compiling 2.2.33.1 and it fails on one of my servers - FreeBSD 8.4 where 2.2.32 has been running happily: This is where I am going to start the tests before I move to the other servers (FreeBSD 9.3, 10.3, 11): mv -f .deps/maildir-settings.Tpo .deps/maildir-settings.Plo /bin/bash ../../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../../..

Sirs, I can't compile the source spandsp-0.0.2pre10; when i try to do the "make" sentence the following errors appear: # make Making all in src make[1]: Entering directory `/export/usr/src/spandsp-0.0.2/src' make all-am make[2]: Entering directory `/export/usr/src/spandsp-0.0.2/src' if /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I. -I -g -O2 -MT