Hi all, I've faced an issue (#557550) which is much probably caused by a CPU which doesn't support SSE2 instructions. I'm not sure about the best way to address this. Any suggestion will be very welcome. Actually I can see the following workarounds:
1) consider that most of CPUs support this flag, so tell the reporter to compile the package by him/herself. 2) remove this specific flag during package building, ending with a non-optimized software available for all users. 3) create a specific -sse2 (or -non-sse2) package. 4) ask the upstream to code runtime checks before using SSE2 specific instructions (is that possible?). For now, my choice is #1. Btw, there is an old proposal [0] related to this subject but I have no ideia how it's going. [0] http://lists.debian.org/debian-devel/2003/06/msg01714.html -- -------------------------------------------------------------------------------- .''`. Tiago Bortoletto Vaz GPG : 1024D/A504FECA : :' : http://tiagovaz.org XMPP : tiago at jabber.org `. `' tiago at {tiagovaz,debian}.org IRC : tiago at OFTC `- Debian GNU/Linux - The Universal OS http://www.debian.org --------------------------------------------------------------------------------
signature.asc
Description: Digital signature
