
stsander at sblan
May 1, 2012, 7:02 AM
Post #3 of 3
(338 views)
Permalink
|
On 04/30/2012 09:09 PM, Anthony G. Basile wrote: > On 04/30/2012 12:10 PM, Stan Sander wrote: >> trap invalid opcode > > Two possibilities: 1) the running program aims its instruction pointer > at some garbage. I doubt it in this case. 2) Uour binaries make use > of op codes that your hardware is not able to handle, like I noticed > your cpu doesn't support ssse3 or sse4. So, for example, if some use > flag triggers code to be compiled that needs those instructions sets, > and you're cpu doesn't support them, you'll hit this error. > > What's missing is your global CFLAGS, CXXFLAGS, CHOST, USE and any > other goodies that might affect how your binaries are getting built. > > Anthony, Thanks for the response. I did some more searching and reading and came to the conclusion the root cause is #2, and I've made a change in my CFLAGS to use -march=native. I'm in the process of an emerge -e just to make sure nothing remains with the old flags. I'll post back how it goes, but it seemed to be a good change to try since it sets/unsets various flags that could lead to the opcode errors. -- Stan & HD Tashi Grad 10/08 Edgewood, NM SWR PR - Cindy and Jenny - Sammamish, WA NWR http://www.cci.org
|