similar to: installing ices2 (fwd)

okay I am having some difficulty getting ices2 installed on freebsd this happens during execution of autogen.sh --- snip --- checking whether ln -s works... yes loading cache /dev/null within ltconfig ltconfig: you must specify a host type if you use `--no-verify' Try `ltconfig --help' for more information. configure: error: libtool configure failed --- snip --- typhoon# uname -a

Hello, I hope this is the place to bug ppl about compile errors. So here I go. I downloaded the latest through CVS last night and ran ./autogen.sh according to the manual and ran into the following error. Does anyone happen to have a fix for it? I am on FreeBSD 4.6 Stable. Thanks in advance, Till << ./autogen.sh output and error message >> elation# ./autogen.sh I am going to run

While diagnosing a problem I was having with IMAP and SSL (which I ended up fixing by simply upgrading from 0.99.9.1 to 0.99.10, and possibly affected by upgrading openssl libs from 0.9.7a to 0.9.7.b), I attempted to try the CVS version of Dovecot. When using the CVS version, apparently I have to first generate 'configure' using autogen.sh (?). This was the result of that, on FreeBSD

Hi all, Don't ask me why but I had to recompile icecast (from CVS) and now I'm getting this: #./configure checking for a BSD compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking whether make sets ${MAKE}... yes checking for working aclocal-1.4... found checking for working autoconf... found checking for working automake-1.4... found

Compiled libbogg and libao using ./configure; make Then moved to libvorbis source folder Installed libtool (1.3.5p3), autoconf (2.52) and automake (1.4-p5). gnu make is also there (3.79.1) i had to create a link for autoconf as after install it was installed as /usr/local/bin/autoconf-new so i added a link from it to /usr/local/bin/autoconf output from ./autogen is: -- $ ./autogen.sh

The file vorbis/ltconfig appears to be checked into CVS. This is an automatically generated file -- it should not be under CVS control. {+} Jeff Squyres {+} squyres@cse.nd.edu {+} Perpetual Obsessive Notre Dame Student Craving Utter Madness {+} "I came to ND for 4 years and ended up staying for a decade" --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project

in the FreeBSD ports there already is something for ices2 and icecast2. it's a little on the old side (from november 2002). cvsup the latest ports tree, though, you should update your box to 4.7 as well ... or 4.8-rc if you really want to be l33t. i've asked the port maintainer to at least put the oddsock yp hack in there or at least to update the port, but he hasn't yet. boink.

Hello, when i try to compile vorbis-tools-1.0rc1 under linux i got this error when i try to run ./configure: Here is the config log: [....] configure:1264: checking for BSD-compatible nm configure:1300: checking whether ln -s works ltconfig:603: checking for object suffix ltconfig:604: gcc -c conftest.c 1>&5 ltconfig:629: checking for executable suffix ltconfig:630: gcc -o conftest

[This mail is a bit long: sorry.] Hi, I have been trying to compile vorbis-tools-1.0beta4 on NetBSD-1.5/i386, and I get the following: --------------------- Upon typing ./configure --prefix=/usr/pkg/ --with-ogg-prefix=/usr/pkg/ --with-vorbis-prefix=/usr/pkg/ --with-ao-prefix=/usr/pkg/ checking for Ogg... yes checking for Vorbis... yes checking for ao... no *** Could not run

I would like to always use ${CC} for linking the main binary and the shlibs. Inspection of configure.in reveals that we currently deviate in the following cases: mainld shlibld aix[2-9]* ld ld alpha*osf* ${FC} -g -nofor_main -fpe3 ${FC} hpux* ${CC} ld Does anyone recall why we do not use ${CC} in these cases? Did anyone successfully build R on these platforms with ${CC} for

Hi, <p>surprisingly easy, I got around the compilation problems. In configure.in I simply set the autoconf requirement to v2.52 and autogen.sh worked. After that, i got ltconfig: you must specify a host type if you use `--no-verify' Try `ltconfig --help' for more information. I removed --no-verify from the configure script, it worked and compiled. maxx@phoenix:~/src/vorbis-tools$

> > > $ aclocal && autoconf && automake -c -a -i > > > aclocal: configure.in: 45: macro `AM_PATH_XMMS' not found in > library > > > > my hunch is that your version of either automake or possibly > > autoconf is not recent enough. > > No. He simply doesn't have xmms installed. That's what I mentioned > a while ago:

On Wed, 6 Jun 2001, Josh Coalson wrote: > > > my hunch is that your version of either automake or possibly > > > autoconf is not recent enough. autoconf v2.13 automake v1.4 I've upgraded to autoconf v2.50 and updated flac from cvs. The error is being generated by aclocal anyway and that's part of automake v1.4. > > No. He simply doesn't have xmms installed.

ltconfig placeholder shoud be removed. Makefile.am : some stuff copied from branch_beta3 ogg lib must be added only where necesary. vq subdir Makefile.am'ized, (but installs nothing) made distclean target slightly more clean -- check it by hand first, please --- also you'll want to remove vq/Makefile if the ...am passes inspection ------------------------------------------------- diff

Dear R Development Core Team R for Mac has been reviewed by Download Typhoon and got "Editor's Pick" award: http://www.downloadtyphoon.com/r-for-mac/infoyvnppyhf Please publish Download Typhoon "Editor's Pick" award on your website by adding the following HTML code: 160 x 80: <a href="http://www.downloadtyphoon.com/" target="_blank"><img

checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for style of include used by make... GNU checking dependency style of gcc...

Hi! On March 17th I posted a message on this list concerning an artifact bug in beta4 that is audible in all available bitrates. It was this rumbling sound in the bass area. I made a demo clip, which still is available at http://www.stud.uni-karlsruhe.de/~us87/ogg/vorbis_bassrumble_demo.rar and that contains both the original .WAV and an .OGG @ 350kbps. This archive is 2.1 MB large. Today, I

Hello, I couldn't help noticing that the debian build system in cvs was changed. As I used to compile and install from cvs, I discovered a small problem regarding autogen.sh. It's called in debian/rules, before the obj-dir is created (and changed into and ../configure is started). At least on my system autogen.sh implicitly runs ./configure, so the original source path is already

Hello -- Some wav files have been crashing the stuff I checked out from cvs last night. Is this happening to anyone else? Red Hat Linux release 7.3 (Valhalla) Kernel 2.4.18-5 on an i686 gcc-2.96-110 glibc-2.2.5-36 Encoding "04_imiuta.wav" to "04_imiuta.ogg" at quality 1.00 [100.0%] [ 0m00s remaining] \Segmentation fault Program received signal

On Tue, 11 Jun 2002 11:51:33 +0400 Andrey Astafiev <andrei@tvcell.ru> wrote: > flac-1.0.3_beta compilation breaks for me with message: I had the same experience, too. I think that a cause is in configure and configure.in files. Therefore, let's rebuild these files. I took the following, and solved the problem. $ cd flac-1.0.3_beta $ automake $ autoconf $ ./configure ;make --