search for: libvorbis_la_libadd

This one may be my fault.... I've put a temporary fix for libvorbis not linking, I altered libvorbis_la_LIBADD = to libvorbis_la_LIBADD = $(OGG_LIBS) in the makefile, hence the temporary and continued with the build. I'm now getting gcc -DPACKAGE=\"libvorbis\" -DVERSION=\"1.0.0\" -DHAVE_ALLOCA_H=1 - DHAVE_ALLOCA=1 -I. -I. -I../include -I/boot/home/config/include -O20 - D__NO...

...MS itself. For instance, here's the Makefile.am for the vorbis plugin: if HAVE_OGGVORBIS lib_LTLIBRARIES = libvorbis.la endif libdir = $(plugindir)/$(INPUT_PLUGIN_DIR) INCLUDES = @GTK_CFLAGS@ @OGG_CFLAGS@ @VORBIS_CFLAGS@ -I$(top_builddir)/intl libvorbis_la_LDFLAGS = -module -avoid-version libvorbis_la_LIBADD = @GTK_LIBS@ @PTHREAD_LIBS@ @VORBIS_LIBS@ @OGG_LIBS@ libvorbis_la_SOURCES = \ vorbis.c vorbis.h \ configure.c \ http.c http.h \ fileinfo.c \ vcedit.c vcedit.h \ utf8.c -- - mdz

...to libvorbisfile_la_LIBADD = libvorbis.la @OGG_LIBS@ Is this correct? I assume that building a shared library on a "real" Unix platform doesn't require every symbol to be defined at build time, but building on Windows does. Or something like that. I noticed that the definition of libvorbis_la_LIBADD already has @OGG_LIBS@ in it, so perhaps this is only an oversight.

This fixes a build problem with libvorbisfile. Aaron Index: lib/Makefile.am =================================================================== --- lib/Makefile.am (revision 9064) +++ lib/Makefile.am (working copy) @@ -19,7 +19,7 @@ libvorbis_la_LIBADD = @OGG_LIBS@ @VORBIS_LIBS@ libvorbisfile_la_SOURCES = vorbisfile.c -libvorbisfile_la_LDFLAGS = -no-undefined -version-info @VF_LIB_CURRENT@:@VF_LIB_REVISION@:@VF_LIB_AGE@ +libvorbisfile_la_LDFLAGS = -no-undefined -version-info @VF_LIB_CURRENT@:@VF_LIB_REVISION@:@VF_LIB_AGE@ @OGG_LIBS@ libvorbisf...

--- Matt Zimmerman <mdz@debian.org> wrote: > The only difference in the command lines seems to be that your > xmms-config > explicitly links with -lgthread, while I suppose mine lets the > dynamic linker > pull it in. The only significant difference between the old and new > _LIBADD > lines is that @XMMS_LIBS@ is at the beginning in the new one. Now > that I think

libvorbis does not currently have any simd/vectorization. Following patches add generic framework for simd/vectorization and on top, add ARM-NEON simd vectorization using intrinsics. I was able to get over 34% performance improvement on my Beaglebone Black which is single Cortex-A8 based CPU. You can find more information on metrics and procedure I used to measure at