Hi, On Sun, Feb 16, 2014 at 07:41:02PM -0500, Reinhard Tartler wrote: > On Sun, Feb 16, 2014 at 7:28 PM, peter green <plugw...@p10link.net> wrote: > > We can't use the neon option because no arm port of debian gaurantees that > > neon will be available. So I belive until the no-fpu options are made > > compatible with audacious and/or some form of runtime detection is > > implemeted (either using ld.so.hwcaps to load different versions of the > > library) we need to keep using --with-generic-fpu on all our arm ports.
Thanks Peter for explaining, this was how I ended up the suggestion in the bug. > I see. In that case, I'll have to leave the package as it until > something along those lines is implemented. Yes. The ideal solution is for the upstream to implement cpu runtime detection that: 1) uses neon if it is available 2) falls back to fixed point if app requested 16-bit playback 3) finally falls back to generic fpu code if neither of above applies Any packaging level workaround is going to be suboptimal for someone. Riku -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
