Hi > So, it seems he doesn't have SSE2 instructions in his processor. The thing is > that your configure.in is supposed to do the proper check before passing the > flags to the compiler. (SSE=$(cat /proc/cpuinfo | grep sse2) ...) > > So, could you guess what's going wrong here?
Yes, the configure.in script does the proper check, that means that if the package maintainer computer (yours) have SSE2, the final debian package will use SSE2, how to fix that? ... edit the configure.in file search for this line: SSE="-msse2 -mfpmath=sse" and change it for: SSE="-msse -mfpmath=sse" Then you need to run the autogen.sh script to generate the configure script. (this autogen.sh is only available in the CVS or git sources), get and copy to your sources. With this changes the final rakarrack binary will use only "sse" even if the computer has "sse2". I think the actual version on the CVS is 0.4.3, we have deprecated CVS, now the development version is 0.5.0 and is only available in git. (check our website for instructions of how to get it.) We have plan to release 0.5.0 soon .. maybe in 1 or 2 months. I have plan also to put some configure option to override the default check for SSE. Josep -- Josep Andreu <holb...@telefonica.net> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
