similar to: [vorbis-tools] Some patches coming from Debian bugs

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:

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

hello all, (cc'ing some other package maintainers) I attached a patch against vorbis-tools-1.1.1 to make the code also compile against the upcoming FLAC 1.1.3, beta available here: http://prdownloads.sourceforge.net/flac/flac-1.1.3-beta2.tar.gz?download changelog: http://flac.cvs.sourceforge.net/*checkout*/flac/flac/doc/html/changelog.html with FLAC 1.1.3 there is no need for EasyFLAC. the

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:

hi! I've got some problems compiling/linking the vorbis tools. at first I had the same problem as mentioned here: http://www.xiph.org/archives/vorbis-dev/200201/0005.html (make was looking for libogg.la in the wrong path) but creating a symlink to /usr/local/lib/libogg.la in /usr/lib/ helped. :) having solved this, I get a new error: --- gcc -O20 -ffast-math -fsigned-char -o ogg123

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

----- Forwarded message from Don Armstrong <don@donarmstrong.com> ----- Date: Thu, 30 Sep 2004 16:19:41 -0700 From: Don Armstrong <don@donarmstrong.com> Resent-From: Don Armstrong <don@donarmstrong.com> To: submit@bugs.debian.org Subject: Bug#274301: libflac4 segfaults on corrupt flac files Severity: normal Package: libflac4 Version: 1.1.0-11 Running ogg123 on

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

Some detailed feedback that looks useful. ----- Forwarded message from Michael Semon <wayfarer42@postmaster.co.uk> ----- Delivery-Date: Tue Jul 16 05:29:37 2002 X-Mailer: MIME-tools 5.41 (Entity 5.404) From: "Michael Semon" <wayfarer42@postmaster.co.uk> Subject: CVS: ogg123 rocks! vcut no so much so... To: feedback@vorbis.com Hi! Being impatient for RC4, I downloaded

hi - I was just trying to build vorbis-tools-1.0beta4 on an irix 6.5 system using the native C compiler (version 7.21, i think). I had to make a few changes to the sources to get the package to compile. There were a couple files that used alloca() but didn't include alloca.h. There was another source that used index(). On irix, you need to include strings.h to get that declared. However, i

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

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",

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 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

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

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, 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

I just moved a bunch of shared code (like 4 copies of getopt) into a share directory within vorbis-tools. I also moved the UTF-8 code from oggenc into the vorbis-tools/share directory as well so that it could be used by all of the tools, since they all need to handle UTF-8 comments correctly. Header files for the shared code are stored in vorbis-tools/include. I have already fixed vorbiscomment

This patch makes Perl strings translatable. The Perl strings end up in the PO files as usual. It does not touch the embedded POD. Internationalizing the Perl strings was pleasantly simple. Just add: use Locale::TextDomain 'libguestfs'; at the top of any *.pl or *.pm file. Then for each string in the file that you want to be translatable you place TWO underscores before it: -

--- COPYING.GPL | 43 +++++++++++----------- doc/Makefile.am | 6 +-- doc/Makefile.lite | 6 +-- examples/c/decode/file/Makefile.am | 6 +-- examples/c/decode/file/Makefile.lite | 6 +-- examples/c/decode/file/main.c | 6 +--