similar to: trouble compiling vorbis 1.0 on openbsd

Displaying 20 results from an estimated 5000 matches similar to: "trouble compiling vorbis 1.0 on openbsd"

2003 Aug 09
3
CVS/test version config/build failures on FreeBSD
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
2003 Apr 01
4
compile error
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
2004 Aug 06
1
error compiling from CVS
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
2004 Aug 06
1
installing ices2 (fwd)
Any ideas please. I want to get this installed! I have the Latest CVS download! 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
2001 Aug 13
2
configure error
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
2003 Jan 12
0
building CVS' vorbis-tools on OpenBSD 3.2
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$
2004 Sep 10
0
Re: beta 10 candidate checked in
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.
2001 May 11
2
artifact bug status? / compiling under OpenBSD 2.8
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
2004 Sep 10
5
Re: beta 10 candidate checked in
> > > $ 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:
2004 Aug 06
0
compile error
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.
2004 Aug 06
2
automake problem
Hi again. Which version of automake is used for the sources of icecast (& co)? Which versions of automake will be able to work with the files on cvs? I'd also like to ask you if some of you got to build the icecast 2 sources correctly with redhat 7.2, 7.3 or 8.0. I am getting the following error doing an ./autogen.sh: I am going to run ./configure with no arguments - if you wish to
2000 Dec 22
1
vorbis/ltconfig
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
2000 Nov 10
1
cvs trunk vorbis/ compile patches
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
2002 Jul 06
3
Can't compile vorbis-tools CVS
Hi all: I haven't had any luck with this on vorbis-dev, so I thought I'd try here. Note that for those who have read this already, there's new stuff at the bottom. I'm getting the folowing when attempting to compile vorbis-tools from CVS: Making all in intl make[1]: Entering directory `/usr/src/cvs/vorbis-tools/intl' make[1]: *** No rule to make target
2000 Jun 23
1
MAINLD and SHLIBLD
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
2002 Feb 16
2
libvorbis config error
Hi all. I found some references to a problem similar to mine in the archives, but none of the solutions posed there worked, so I'm left to ask again. I'm running Debian 2.2r5, libc6, and as far as I know all other necessary libraries for compilation. libao and libogg compile and install fine, but when I try run ./configure for libvorbis, it fails and says it can't find libogg.
2001 Mar 13
1
Compiling vorbis-tools on NetBSD-1.5/i386
[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
2002 Jul 03
3
segfault in current cvs
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
2004 Sep 10
2
flac-1.0.3_beta released
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 --
2002 Sep 11
0
libvorbis install problem
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...