similar to: vorbis-tools ./configure problems libao2 posix threads

Hi Heikki, So libao is currently not maintained upstream. In the appropriate IRC channels I'm lead to believe that there are better libraries out there that should be used instead. If so many debian packages didn't link against it I would seriously consider dropping it all together. It doesn't sound like it's worth anyone's time maintaining libao properly upstream. I do have

happy new year. a day off is a day to pick up a new project, so I wrestled my way through making ogg vorbis work on macosx. first, libao (not entirely a proper patch, but 2 source file diffs and a diff of a configure'd Makefile to one that works.): http://bolson.org/pub/libao-0.8.2-diff.tar.gz libogg and libvorbis compiled without incident. vorbis-tools were more complicated. I think

happy new year. a day off is a day to pick up a new project, so I wrestled my way through making ogg vorbis work on macosx. first, libao (not entirely a proper patch, but 2 source file diffs and a diff of a configure'd Makefile to one that works.): http://bolson.org/pub/libao-0.8.2-diff.tar.gz libogg and libvorbis compiled without incident. vorbis-tools were more complicated. I think

Hello, I built the entire Vorbis kit on my PowerMac G4 running OSX 10.4.6. I'm having problems however doing anything with the libao package. Any time I try to use the library to link it errors out with the following message: /usr/bin/ld: Undefined symbols: _dlsym_auto_underscore collect2: ld returned 1 exit status If I try to run the ogg123 application I get this:

I installed fink and now I have the /sw/lib, however that didn't fix my problem. I went as far as to take out the - Ddlsym=dlsym_auto_underscore out of the configuration files. Now however the libao package won't build at all and yips about this: [ukiel:/MP3/OGG/libao-0.8.6] wind% make Making all in src Making all in plugins Making all in oss make[3]: Nothing to be done for

Hi there, I've been grappling with this for some time, so I'm finally breaking down and trying this list. I'm trying to integrate libvorbisfile and libao to create a simple sound file player, a la ogg123. To do this, I borrowed heavily from ao_example.c and vorbisfile_example.c. I feed the buffer from ov_read into ao_play in a simple loop. It usually works, but occasionally all it

hi, i am trying to load vorbis tool on to my arm board EDB9302 , till now i have cross compiled libao, libogg, libvorbis, flac, speex and vorbis tool. when i run the command line arm-linux-ogg123 with some sample ogg format file on my arm board it gave *"Could not load default driver and no driver specified in config file : Exiting"* , please help me to over come this error.

Hi All, For my new file (and thus mp3) server I've decided to switch completely to Ogg Vorbis. This means having to reencode ~30GB worth of 128Kb MP3's, but i figured that it would all be worth the effort. So I downloaded the sources for libogg, libvorbis and vorbis-tools and fired up my trusty old compiler. libogg and libvorbis built and installed like a charm. Not so for

I saw that libao has a NAS plugin and wanted to try it out, especially with ogg123. However, I had/have several problems. My platform is Solaris 9/SPARC 12/02, NAS 1.6, libao 0.8.5, curl 7.10.8, libogg 1.1, libvorbis 1.0.1, and vorbis-tools 1.0.1. PROBLEM ONE: ------------ I had to specify LDFLAGS="-lXt -lsocket -lm" before running ./configure with "--enable-nas" in order

Hi, I noticed there was some discussion on this list about the desire for ogg123 to support output to stdout via Sun's .au file format, so I decided to give implementing an AU driver for libao a shot. Here is my first attempt. To test the driver: * Apply the patch below (against ao in CVS) * Copy the attached ao_au.c into ao/src * Run ao/autogen.sh, compile, and

I have got libao up to oggenc and ogg123 working on Mac OS X Public Beta now. I'd like to submit patches, but last time I did, they never got committed by anyone. Who is in charge of committing stuff? Does someone want to nominate themselves to review and commit my patches? The patches are briefly: - On Mac OS X dlopen() is not very well supported, so libao has been cleaned up a bit to

Hello, I have written a libsndfile (http://www.mega-nerd.com/libsndfile/) file output plugin for libao. For the moment I haven't done any changes to the core of libao. However some changes could make this more useful. Before I embark on anything like this I'd like to have your opinion on a few things. --- First, what do you prefer ? 1a. Keeping the AU/WAV/RAW plugins and adding

I submitted four new packages for the NetBSD pkgsrc collection: libao, libogg, libvorbis and vorbis-tools for 1.0beta4. The following is some of the patches needed for libao and vorbis-tools. Official Developers: When you receive patches or development suggestions can you please acknowledge them? (For example: "Noted.", "Thanks, but already done.", "Not necessary,

On 16-01-13 21:52, Clemens Ladisch wrote: > Rene Herman wrote: >> I'm out of touch of with alsa -- but should dmix/dsnoop still be >> enabled by default on hardware that doesn't do hardware mixing? > > Yes. > >> I believe that it should be from /usr/share/alsa/cards/ICH4.conf, >> but I don't get mixing on this setup when using the

So I'd like to try out rc3 (been a happy user of rc2 since it came out). I download the RPMS and try to do an upgrade, only to find that libao and vorbis-tools depends on 'libcurl' and 'libasound' which are not part of Red Hat 7.1 (looks like curl is in 7.2, but God knows where to get libasound). In addition, the RPMs want libcrypto.so.0, while 7.1 and 7.2 have .1. So

Hello, I am trying build vorbis-tools-1.1.1 in the framework of my tool (see signature). The essence of the tools is that it builds and install everything locally, and, of course, it uses the available mechanisms to specify search paths for both headers and libraries; the tool first builds dependencies abd then the target itself. So, for example, 'configure' for vorbis-tools-1.1.1 is

Here is a patch to fix the compiler warnings I mentioned earlier. I've removed the byte-order changes that don't make sense. (Thanks Michael for pointing out the error!) As for the byte-order changes, since some output modules don't have the option to set the sample byte-order, I would like to standardize libao and ogg123 on native byte-order. Will this break the ao_wav.c patches

I'm having several problems with ogg123 on a FreeBSD-STABLE machine. In each case, ogg123 dumps core complaining about a bus error. 1) ogg123 plays all files at what seems like twice the correct speed. When given a SIGINT, ogg123 dumps core. This is using the program defaults, including the OSS driver. Here's a backtrace from gdb: Core was generated by `ogg123'. Program

Just as a reminder to our application maintainers. ----- Forwarded message from Ryan Cooley <ryancooley@yahoo.com> ----- Delivery-Date: Sun Jul 22 20:28:06 2001 From: Ryan Cooley <ryancooley@yahoo.com> Subject: Problems with ogg123 on OpenBSD To: feedback@vorbis.com While I hate to send complaints about something that is Free(tm), I really hoped and expected the Ogg Vorbis team to

I was just curious about the patch that I sent for ogg123 that implements the --quiet and adds in the --skip option? Also - I would like to know what are the main cvs modules and branches in which development takes place? Specifically, I would like to look at the very latest libao and ogg123 sources. I would also like to know where the main development for libvorbis takes place Regards, Ali