How come this bug has not been fixed yet? As Scott Talbert noted this can be done by adding --disable-sse3 to the configure flags, at least for 32-bit x86 builds.

If you don't think people still use CPUs without SSE3 support, look at this bug report and duplicates: [1]

Other major distributions have fixed this bug in their packages. [2] There is also an upstream bug report [3], but it has not received any response so far.

So, what is preventing this from getting fixed?


Daniel

[1] https://bugs.arx-libertatis.org/arx/issues/218
[2] http://wiki.arx-libertatis.org/Upstream_bugs_under_Linux
[3] http://sourceforge.net/tracker/?func=detail&aid=3520344&group_id=4470&atid=104470

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to