[N.B. Sent to Lame mailing-list and to Rogerio Brito (who appears in the debian/control file)]
I finally got the Round Tuit required to build Lame 3.92 on my Debian system last night (until now, I've been using a November 2001 snapshot). I was pleasantly surprised to find a debian/ directory in the source tarball, so I decided to take advantage of this and build a package so I could safely install into the managed part of my machine(s). A couple of things I noticed: * The package is version 3.91-1, but we're packaging Lame 3.92 * I was able to build mp3x by installing libgtk1.2-dev as a Build-Depends, and adding --enable-mp3x to the configure rule in debian/rules. (N.B. libgtk2.0-dev *does not* work by default, as it's missing gtk-config) I also needed to add usr/bin/mp3x to debian/lame.files If I knew how to do it, I'd try making a separate package lame-mp3x so as not to pull in Xlib for users who want only Lame. * I added --enable-expopt --enable-nasm to the configure line successfully (I tried --enable-expopt=full, but that requires a newer gcc than the 2.95 that's in sarge - dunno why configure doesn't test the compiler options). I didn't try --enable-analyzer-hooks, --enable-mp3rtp or --with-vorbis. Is it possible (and legal) to distribute the source package as part of Debian, without compiling it to binary packages? _______________________________________________ mp3encoder mailing list [EMAIL PROTECTED] http://minnie.tuhs.org/mailman/listinfo/mp3encoder
