Bug#713966: nvidia-texture-tools: OptimalOptions.cmake assumes x86_64 implies athlon64

So the testsuite works fine when nvtt is not optimized for athlon64? On 24.06.2013 13:33, Vincent Cheng wrote: Package: src:nvidia-texture-tools Version: 2.0.8-1+dfsg-3 Severity: important Tags: patch Control: block 712956 by -1 Dear Maintainer, As reported in #712956, one of the amd64

Bug#713966: nvidia-texture-tools: OptimalOptions.cmake assumes x86_64 implies athlon64

On Tue, Jun 25, 2013 at 6:57 AM, Lennart Weller lenn...@lennartweller.de wrote: So the testsuite works fine when nvtt is not optimized for athlon64? I can't say 100% for sure, but I suspect that this is the cause behind the testsuite failing on barber (this is difficult for me to confirm since

Bug#713966: nvidia-texture-tools: OptimalOptions.cmake assumes x86_64 implies athlon64

Package: src:nvidia-texture-tools Version: 2.0.8-1+dfsg-3 Severity: important Tags: patch Control: block 712956 by -1 Dear Maintainer, As reported in #712956, one of the amd64 buildds (barber) fails to execute 0ad's testsuite (causing a FTBFS) due to some sort of Illegal instruction. After

Bug#713966: nvidia-texture-tools: OptimalOptions.cmake assumes x86_64 implies athlon64

Also, this bug is reported to upstream nvtt as [1]. Unfortunately Gmail likes to wrap stuff and control@b.d.o doesn't like that, so I'm having troubles marking this bug as forwarded... [1] https://code.google.com/p/nvidia-texture-tools/issues/detail?id=188 -- To UNSUBSCRIBE, email to