Your message dated Sat, 22 Mar 2014 19:09:41 -0700 with message-id <[email protected]> and subject line Re: Bug#724727: gnubg: fails to detect SSE at runtime has caused the Debian Bug report #724727, regarding gnubg: fails to detect SSE at runtime to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 724727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724727 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: gnubg Version: 1.01.003-1 Severity: important Dear Maintainer, when I run gnubg, I get this error: This version of GNU Backgammon is compiled with SSE support but this machine does not support SSE However, this machine does have SSE: $ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 8 model name : AMD Athlon(tm) XP 2200+ stepping : 1 cpu MHz : 1814.391 cache size : 256 KB fdiv_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes 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 bogomips : 3628.78 clflush size : 32 cache_alignment : 32 address sizes : 34 bits physical, 32 bits virtual power management: ts I first saw the issue when version 1.01.003-1 hit Jessie, and it wasn't solved with version 1.02.000-1 (currently in Jessie). Prior versions worked well. Root cause could be found in this change: * Drop special per-architecture handling of --enable-sse. Upstream now probes for this during configure and at runtime and should do the right thing. Well, apparently it doesn't! Matteo -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.10.5 (PREEMPT) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnubg depends on: ii debconf [debconf-2.0] 1.5.51 ii gnubg-data 1.02.000-1 ii libc6 2.17-92+b1 ii libcairo2 1.12.14-4 ii libcanberra-gtk0 0.30-2 ii libcanberra0 0.30-2 ii libfreetype6 2.4.9-1.1 ii libgdk-pixbuf2.0-0 2.28.2-1 ii libgl1-mesa-glx [libgl1] 9.1.6-2 ii libglib2.0-0 2.36.4-1 ii libglu1-mesa [libglu1] 9.0.0-1 ii libgmp10 2:5.1.2+dfsg-2 ii libgtk2.0-0 2.24.20-1 ii libgtkglext1 1.2.0-3.1 ii libpango-1.0-0 1.32.5-5+b1 ii libpangocairo-1.0-0 1.32.5-5+b1 ii libpng12-0 1.2.49-4 ii libpython2.7 2.7.5-5 ii libreadline6 6.2+dfsg-0.1 ii libsqlite3-0 3.8.0.2-1 gnubg recommends no packages. Versions of packages gnubg suggests: pn kbackgammon <none> -- debconf information: gnubg/build-bearoffs: false
--- End Message ---
--- Begin Message ---Version: 1.02.000-2 Russ Allbery <[email protected]> writes: > 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. Fixed as noted in 1.02.000-2, where all SIMD types are disabled for i386. -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/>
--- End Message ---
