You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Building using "cmake . && make" on Fedora 7 x86_64
What is the expected output? What do you see instead?
It should build normally, but instead:
[per@localhost nvidia-texture-tools]$ make
Scanning dependencies of target nvcore
[ 2%] Building CXX object src/nvcore/CMakeFiles/nvcore.dir/Memory.o
/home/per/devinstall/nvidia-texture-tools/src/nvcore/Memory.cpp:1: error:
CPU you selected does not support x86-64 instruction set
/home/per/devinstall/nvidia-texture-tools/src/nvcore/Memory.cpp:1: error:
CPU you selected does not support x86-64 instruction set
make[2]: *** [src/nvcore/CMakeFiles/nvcore.dir/Memory.o] Error 1
make[1]: *** [src/nvcore/CMakeFiles/nvcore.dir/all] Error 2
make: *** [all] Error 2
What version of the product are you using? On what operating system?
Both version 0.9.4 and svn trunk revision 76 fail as above.
Please provide any additional information below.
Patch that should fix the problem is attached. It detects g++ and sets the
use of SSE3 in a way that should not break with x86_64 processors.
Original issue reported on code.google.com by per.math...@gmail.com on 18 Aug 2007 at 10:25
Whops! Thanks for catching that. I used to comment/uncomment that line locally
according to the system where I'm working from, and probably submitted it by
error.
I've added the gnucxx compiler check and left all the custom options commented
out.
I wish there were a cmake script that set the optimal options for the current
system
automatically. I wonder how does gentoo do that... I guess you could do `uname
-m` or
`cat /proc/cpuinfo`, and have a table with predefined options for each supported
machine type.
These seem to be the ones used in gentoo:
http://www.freehackers.org/gentoo/gccflags/flag_gcc3.html
Original comment by cast...@gmail.com on 20 Aug 2007 at 10:49
Original issue reported on code.google.com by
per.math...@gmail.com
on 18 Aug 2007 at 10:25Attachments:
The text was updated successfully, but these errors were encountered: