Now that I've had another look at this, I realized a couple other things. First, your architecture is i386, not amd64 (I'd gotten confused by the fact that you have an AMD processor, but of course that's not related). That means that this problem actually should be fixed in 1.02.000-2, where I disabled all the SIMD types for i386 builds.
Second... > However, this machine does have SSE: > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge > mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow ...yes, but what gnubg means by SSE in this particular case is actually SSE2, which you don't have. I think 1.02.000-2 will fix gnubg on this system. This would have indeed been broken since 1.01.003, since I had gotten confused by how the runtime testing was working. I had thought that gnubg was testing at runtime and falling back on non-SIMD code, but it was just testing at runtime and then refusing to run. Somewhat less useful for generic Debian builds than I was hoping. :) -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
