I wrote this script to automate creating a static oggenc build. [1] I call it "mkoggenc.sh".

You are supposed to unpack the aoTuV and vorbis-tools tarballs, and run it like this: "./mkoggenc.sh aotuv-b6.02_20110227 vorbis-tools-1.4.0" (the directories they unpacked to). It worked for me at least on aoTuV 6.02 and vorbis-tools 1.4.0, on Debian Squeeze.

if [ -x oggenc/oggenc ]; then echo "Your shiny new oggenc is located at:" echo $BASE/$TOOLS/oggenc/oggencfi

I notice it breaks if there's any whitespace in the directory path. Ah well.

[1] It's not completely static -- but at least the aoTuV library is linked to statically, which should be enough. And you do need the relevant dev packages installed, e.g. to compile in FLAC support. "apt-get build-dep libvorbis vorbis-tools" should do it.

I've just found this thread after compiling the AotuV b6.03 for my old ibook with new debian installed. After installing the AotuV version of libvorbis on /usr/local I had the same problem: the old oggenc would use the libraries supplied by the debian libvorbis package (on /usr/lib). Googling I just found this page (http://www.cyberciti.biz/faq/linux-setting...g-library-path/) which explains how to specify the libraries you want to use with oggenc.

If you have two libraries with the same name then the path is evaluated in a series of steps. You can override the whole lot by specifying the preffered order in LD_LIBRARY_PATH, but that's best kept for testing.

After that, ldconfig evaluates paths starting with the system defaults in /etc/ld.so.conf and moving on to paths in /etc/ld.so.conf.d/. You can edit these to have /usr/local/lib come first. Remember to run ldconfig (as root) afterwards. Adding a file with /usr/local/lib into /etc/ld.so.conf.d/ probably won't do the trick since it will still come after the default path where the original libraries live. Possibly on your machine the system libraries are in an architecture-specific path such as /usr/lib/i386-linux-gnu, set from a file in /etc/ld.so.conf.d/, in which case the path order depends on alphabetical order of the filenames. You can use a file with a number on the front to make sure you come first.

All of which is great fun and I hope you learned something, but it would be so much better to be able to uninstall the old libraries because you just don't want to use them. You probably can't because there are dependencies on them, for example the libavcodec libraries need them, probably others too. To replace them you would need to create three deb packages called libvorbis0a, libvorbisenc3, and libvorbisfile2, containing your new builds. Then install those which will replace the originals and you'll have no worries about paths.