Bug#712956: marked as done (0ad: seems to use CPU features not available everywhere)

[Vincent Cheng]

On Sat, Sep 7, 2013 at 1:02 AM, Kurt Roeckx <kurt at roeckx.be> wrote:
> reopen 712956
> thanks
>
>>  nvidia-texture-tools (2.0.8-1+dfsg-4) unstable; urgency=low
>>  .
>>    [ Fabio Pedretti ]
>>    * Add armel and armhf build support (Closes: #721972)
>>    * Remove -march=athlon64 from CXXFLAGS (Closes: #713966, #712956)
>
> This is clealy the wrong bug you're closing.  It's assigned to
> 0ad.
>
> 0.0.14-2 is still using -msse -march=i686 on i386

See explanation by upstream here [1]. If compiling with -march=i686 is
strictly not allowed on Debian i386, I can just simply stop building
0ad for i386, although I'm not sure if that's necessary at all; the
package has been sitting in the archive for over a year and I still
haven't gotten any complaints about 0ad not running on any Debian
user's i386 machine.

> It wasn't using -march=athlon64 on amd64 before either as far as I
> know but had problem running on at least one of the buildds.

The original issue was that nvidia-texture-tools was compiled with
-march=athlon64, which caused one of the amd64 buildds to complain
about an "Illegal instruction" when trying to run 0ad's test suite
when building 0ad. There's a relevant issue filed against upstream
nvidia-texture-tools about this as well. [2]

Regards,
Vincent

[1] http://trac.wildfiregames.com/ticket/1994#comment:5
[2] https://code.google.com/p/nvidia-texture-tools/issues/detail?id=188