similar to: patches for building vorbis-tools on irix with sgi cc

This patch cleans up the vorbis-tools Makefile.am files so they work with both automake 1.4 and 1.6. Some changes to configure.in were also needed in order to get things to work (and to fix some ac 2.50 issues). Please remove config.h from cvs as it is a generated file and empty anyway. automake 1.6 isn't really incompatable with 1.4, it's just more picky about you sticking to the rules:

Hello. Attached are some patches that some Debian users of vorbis-tools have sent to our BTS over the years (numbers refer to Debian bugs). It'd be nice to see them integrated. They apply cleanly to SVN as of today. The largefile_support one is a bit bigger than just the configure.ac since the submitter adviced that config.h got included in all C source files before the standard includes,

Hello. Attached are some patches that some Debian users of vorbis-tools have sent to our BTS over the years (numbers refer to Debian bugs). It'd be nice to see them integrated. They apply cleanly to SVN as of today. The largefile_support one is a bit bigger than just the configure.ac since the submitter adviced that config.h got included in all C source files before the standard includes,

There's some compilation issues on Solaris with the native compilers with the current CVS head. OGGENC: ======= -- "oggenc.c", line 202: warning: improper pointer/integer combination: op "=" I believe the problem here is that rindex() is prototyped in <strings.h>, which is not included. This may be a sun-specific thing. OGG123: ======= -- "ogg123.c",

Since vorbiscomment is being resurrected in a new form, can someone please fix the vorbis-tools/vorbiscomment/Makefile.am? There's two things wrong: 1. Using _LDFLAGS doesn't allow the user to specify their own LDFLAGS. _LDADD or _LIBS should be used instead. 2. The order of libraries is wrong such that it won't link properly when compiled statically. Here's a trivial

I've checked out the latest cvs sources of: ao ogg vorbis vorbis-tools I configured/made/installed ao, ogg and vorbis without any problem. I also ran ldconfig after installing the libraries. But when compiling vorbis-tools it broke with: vcomment.c: In function `main': vcomment.c:84: `LOCALEDIR' undeclared (first use in this function) vcomment.c:84: (Each undeclared identifier is

I sent a message about 2 weeks ago about build problems at the head of the CVS tree with non-gcc compilers on POSIX systems, although I didn't correctly identify the link problems as being static-library only (see my previous mail about "static link broken"). Some problems have been fixed, but some still seem to be there. I have edited my original mail to list the problems that

I don't think that the getopt_long() situation is handled correctly in the vorbis-tools module. Here's my take (comments welcome!). ----- This applies to oggenc, ogg123, and vorbiscomment. See http://www.xiph.org/archives/vorbis-dev/200012/0359.html for background and prior discussion on this issue. There are 2 issues: 1. Summary: getopt() is a POSIX function. It will already be on

vcomment.c contains this line: fprintf(stderr, "Vorbiscomment " VERSION "\n"); I can't figure how / where VERSION is defined. <p> -- -:-:- David K. Gasaway -:-:- XNS : =David K Gasaway -:-:- Email: dave@gasaway.org -:-:- Web : dave.gasaway.org <p><p>--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage:

Dear vorbis-dev lurkers, I bring you the first beta release of vorbis-tools 1.3.0. It has quite a few new features and the final version will have even more, so I am sure it is to everyone's benefit that it gets as much tested as possible so we can do a quick release. Here's the changelog so far: * Fixed an error in configure.ac; --with-speex/flac work again (#1319) * Corrected

I've attached updated patches (against vorbis-tools 1.3.0b3.5) to support comment padding. No changes to libvorbis are necessary. The padding is added in the same way as oggenc2 (null bytes within the packet, at the end) and shouldn't cause problems with any reasonable decoder or comment editor implementations. Padding is enabled by default, except for small files (less than 30 s for

Here's a propsed heavy-duty solution for your UTF-8 problems. I'm including a patch in this message, but I'll put the new files on my web site at http://rano.org/tmp/xiph_files.tar.gz I've tested this by running vorbiscomment with and without -DHAVE_ICONV=1 in vorbis-tools/share/Makefile. It seems to work. Changed files: acinclude.m4: Add a test for nl_langinfo(CODESET). This

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

For some reason this didn't make the list and I got no approval message... this time I'll force the From to be my subscribed address. Bug in Monty's new filtering system? Anyway, here goes again. ----- Forwarded message from ----- Date: Thu, 1 Aug 2002 10:24:46 -0400 To: vorbis-dev@xiph.org Subject: Re: [vorbis-dev] [fwd] CVS: ogg123 rocks! vcut no so much so... (from:

Below is a patch for vorbis-tools-1.0beta4 ogg123. It adds support for using the rc file (like /etc/ogg123.rc) for configuring the device-options. In addition, comments can be used (when they start a line). My ~/.ogg123rc: default_device=oss default_options=dsp:/dev/audio Please share your comments. Jeremy C. Reed http://www.reedmedia.net/ diff -u

Again, Hi All, Thanks for your replies. I probably should've mentioned that I'm not subscribed to the list but I found your answers on the archives. I just wanted to go on record and mention that I do in fact have all the original CD's and that by re-encoding I meant repeating the entire process of ripping the original CD's (with cdparanoia (of course ;)) and then encoding them

I think that vorbiscomment should really use -c "this=that" to specify tags on the commandline, consistent with oggenc. That displaces the tag source file, so I'd suggest -f, consistent with at least some other programs (although I can only think of tar, right now). I'd also suggest that it use -o for an output filename rather than splattering the second file on the

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

Hi, Attached are patches for the beta 4 distribution, fixing minor problems in RPM spec files. One question: are there any reasons not to include vorbiscomment in the vorbis-tools binary package? I've added the long-awaited utility program into the revised spec file, but I wonder if it is a wrong change... Regards, -- KAJIYAMA, Tamito <kajiyama@grad.sccs.chukyo-u.ac.jp> diff -ru

Not sure if this is the right place to post this... I have attached a patch for the build system which lets FLAC build on IRIX and Cygwin. -------------- next part -------------- ? Makefile ? aclocal.m4 ? autom4te.cache ? config.guess ? config.log ? config.status ? config.sub ? configure ? depcomp ? install-sh ? irix.patch ? libtool ? libtool-disable-static ? ltmain.sh ? missing ? mkinstalldirs ?