similar to: ao hard codes -ldl in configure tests

Displaying 20 results from an estimated 10000 matches similar to: "ao hard codes -ldl in configure tests"

2001 Mar 16
3
Patches for NetBSD
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,
2001 Jan 29
2
Mac OS X / Darwin patch for vorbis-tools
This patch (along with all the previous patches) gets oggenc and ogg123 working. This does not get vorbiscomment working, although I assume that would be trivial -- just add the getopt stuff to the project just like I did in ogg123. In addition to this patch, as I just mentioned, getopt1.c getopt.h and getopt.c need to be copied from oggenc to ogg123 and added. The host check in
2001 Apr 08
1
Compiling vorbis-tools on FreeBSD
Hi there, I'm having some problems compiling vorbis-tools on FreeBSD 4.2-STABLE. My configure line is ./configure --with-ogg-prefix=/usr/local \ --with-vorbis-prefix=/usr/local \ --with-ao-prefix=/usr/local --prefix=/usr/local I have to put the --prefixes in because I don't know how to tell the compiler to look in /usr/local/include instead of just in /usr/include. Without the
2002 Jan 02
2
macosx (lots of little changes)
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
2002 Jan 02
2
macosx (lots of little changes)
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
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
2000 Dec 15
1
AIX + ogg123
Has anyone managed to get ogg123 to compile in AIX? I'm got an RS6k with a PPC 604e, running AIX 4.3.3. I can get libogg, libvorbis, libao, oggenc (so, everything _but_ ogg123) to compile just fine. I'm using gcc, thankfully, and not the native IBM compilers. I believe the problem to be with the linker. By default gcc for AIX doesn't use the GNU linker, but the standard AIX
2003 Jan 16
1
Several problems with ogg123
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
2001 Nov 04
5
ogg123 running under MacOS X
I finally managed to compile ogg123 under MacOS X, after creating a PB project for it. Rillian, do you want to include the PB project in cvs? (it needs a LOT of polishing, though). ---------- Ogg123 from PACKAGE VERSION by Kenneth Arnold <kcarnold@arnoldnet.net> and others Usage: ogg123 [<options>] <input file> ... -h, --help this help -V, --version display
2001 Oct 23
4
Problems compiling under OS X
While trying to compile libao 0.8.0 under OS X 10.1, I got the following problems: > [localhost:ecc/Sources/libao-0.8.0] root# ./configure > creating cache ./config.cache > 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... found >
2001 Oct 24
3
Almost there...
Ok, I managed to compile the Ogg and Vorbis libs. Then, after modifying the file audio_out.c as follows: original: #include <dlfcn.h> modified: #include <win32/include/dlfcn.h> I was able to (finally!) compile libao. Then I tried to compile the module vorbis-tools, but uninvited problems came to my party. [...] > /usr/bin/ld: multiple definitions of symbol _getopt >
2001 May 08
2
libao AU driver
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
2000 Dec 29
5
build process patches
Here's an updated set of patches to fix some problems with the build process. These patches are relevant to the CVS head as of 30 Dec 2000. Overview: - Patch 1: Allowing the user to set CFLAGS/LDFLAGS before running configure in all four modules. All these patches do is essentially: cflags_save="$CFLAGS" ldflags_save="$LDFLAGS" # ... stuff to
2006 Oct 04
3
problem using libao on OSX 10.4
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:
2001 Feb 27
1
libdl and building under NetBSD
I am trying to configure vorbis-tools-1.0beta. (I already built libvorbis, libao, and libogg.) This is under NetBSD 1.5.1_ALPHA i386. My plan is to create NetBSD packages for Ogg Vorbis. My config.log has: configure:1897: gcc -o conftest -I/usr/local/include -I/usr/local/include -L/usr/local/lib/ -L/usr/pkg/emul/linux/ conftest.c -L/usr/local/lib -lao -ldl 1>&5 /usr/bin/ld: cannot
2006 Oct 06
1
problem using libao on OSX 10.4
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
2008 May 30
3
regarding vorbis tool
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.
2001 Jan 27
4
ogg123 oss plugin plays garbage
I tried to use the current cvs version of ogg123 with oss output and the ogg just sounds like static. I wanted to document it on the list in case anyone else is having the problem. I can make ogg123 write wav files fine. Also Vakor does not have any trouble playing oggs with ogg123, so I am not certain what the problem is. I have tried compiling all of ogg vorbis (ao,ogg,vorbis,vorbis-tools)
2001 Aug 21
2
ao changes
Why has ao been changed so that there are now two open() functions ? IMHO the original ao_open() was fine - if you wanted to set the filename for output, you could add an option via ao_append_option and if you wanted to avoid overwriting an existing file, you could stat() it yourself. Having ao_open_live() and ao_open_file() just makes more work for the user of the library for no gain, AFAICT.
2001 Aug 21
2
ao changes
Why has ao been changed so that there are now two open() functions ? IMHO the original ao_open() was fine - if you wanted to set the filename for output, you could add an option via ao_append_option and if you wanted to avoid overwriting an existing file, you could stat() it yourself. Having ao_open_live() and ao_open_file() just makes more work for the user of the library for no gain, AFAICT.