On Sun, Feb 16, 2014 at 5:46 AM, Thomas Orgis <thomas-fo...@orgis.org> wrote:
> Sorry for being late to the party, but I have to say that this is a
> rather unfortunate situation now.
Thomas, in libavcodec, we "solve" (or rather, workaround, depending on
the PoV) this problem by compiling the libraries multiple times and
installing the resulting variants in different subdirectories:
/usr/lib/arm-linux-gnueabi/libavcodec.so.54
/usr/lib/arm-linux-gnueabi/neon/vfp/libavcodec.so.54
/usr/lib/arm-linux-gnueabi/vfp/libavcodec.so.54
/usr/lib/arm-linux-gnueabihf/libavcodec.so.54
/usr/lib/arm-linux-gnueabihf/neon/vfp/libavcodec.so.54
This way, the run-time linker will pick-up the right version depending
on whatever capabilities the kernel autodetected at run-time. Would it
be possible to do something like this for mpg123 as well? This would
then require to compile
/usr/lib/arm-linux-gnueabi/libmpg123.so.0
for different flavors. However, we would need to make sure that
/usr/bin/mpg123 works with any of them. I'm wondering if this pattern
wouldn't work for mpg123, but I'm not familiar enough with the
codebase to say if this would work. Can you please comment?
--
regards,
Reinhard
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
