On Tue, 18 Jan 2011, Alexander B. Gedranovich wrote:
Hello, Allin.
You was right: --disable-sse2 had helped.
Additional information:
==============================
ales@opensuse:~>uname -a
Linux opensuse 2.6.34.7-0.7-default #1 SMP 2010-12-13 11:13:53 +0100 i686
athlon i386 GNU/Linux
ales@opensuse:~> gcc -dumpversion
4.5
==============================
./configure & make outputs are attached.
Thanks, Alexander. It seems, though, that the configure output you
attached is from a run where you did --disable-sse2 (and got a
working executable) -- is that right?
What I'm really interested in is what's going on when you don't
explicitly disable sse2 (and get a non-working binary). The result
of
cat /proc/cpuinfo | grep sse
might also be of interest.
Allin