severity 428375 important thanks This is affecting other packages too, btanks is one of them.
Ubuntu has a patch for this issue here: http://patches.ubuntu.com/o/openal/openal_1:0.0.8-4ubuntu2.patch -- bye, pabs http://wiki.debian.org/PaulWise
--- Begin Message ---В Сбт, 10/11/2007 в 11:37 +0930, Paul Wise пишет: > Hi, > > About [1] and [2], could you please file a bug on Debian and upstream > OpenAL with the patch you made to fix the issue? I tried to get the > patch from the packages, but you didn't provide any source code for it. > > 1. http://bugs.debian.org/442411 > 2. http://sf.net/support/tracker.php?aid=1777107 I explained openAL problems in a letter, but actually I'm not much mail-lists person. Hope someone file bug agains openAL package. I've send the following text to [EMAIL PROTECTED] , I have no idea where, how and when my text would appear there. :))) So feel three to forward my letter to openAL or btanks mail lists. > Hello everybody. > I'm the person who "fix" openal for the Battle Tanks project and > uploaded fixed packages here: > http://dump.iof.ru/people/megath/openal/ > > But actually I *DID NOT* patch any significant openAL code, I've just > replaced > > #ifdef __MMX__ > > with > > #if 0 > > (seems to be __MMX__ was defined by gcc, not autotools) > > Since OpenAL MMX support is really broken and weird, disabling MMX at > all does not affect perfomance for me(athlon x2 4200+), at least for > battle tanks. And I'm really > "throw-away-all-that-anciend-assembly-because-gcc-does-this-better-than-hackers" > person :) > > The proper way of fixing this is patching autotools scripts for openal > and add something like "--disable-mmx" or "--disable-assembly" > configure > switches, but unfortunately I do not understand autotools well and > cannot quickly hack it, sorry :( > > I did not released source because it became a complete mess after my > intrusion. :) > I hope OpenAL maintainers are aware of this problem.
--- End Message ---
signature.asc
Description: This is a digitally signed message part
