2013/8/16 Walter Dnes <waltd...@waltdnes.org>
> On Fri, Aug 16, 2013 at 03:18:35PM -0300, Francisco Ares wrote
>
> > You were right. I have overlooked the type of the new machine's CPU (it
> is
> > a "Pentium(R) Dual-Core CPU" and the other one, already working, is a
> > "Intel(R) Core(TM)2 Duo CPU"). So, a "march=nocona" instead of a
> > "march=core2" seems to have solved the problem.
>
> I have the following in make.conf
>
> CFLAGS="-O2 -march=native -fomit-frame-pointer -pipe -fno-unwind-tables
> -fno-asynchronous-unwind-tables"
> CXXFLAGS="${CFLAGS}"
>
> ...where "-march=native" will always work correctly for a local build.
> The only possible worry is if you're cross-compiling and or distributing
> a binary to multiple machines. It also saves me the headache of
> figuring out the CFLAGS setting whenever I get a new machine. You still
> have to set up the correct processor in the kernel, however.
>
> --
> Walter Dnes <waltd...@waltdnes.org>
> I don't run "desktop environments"; I run useful applications
>
>
Yes, that is the problem. I got the oldest CPU on witch the same binaries
will run. The newest uses an Intel I3, but the oldest ones run on a "Dual
Core" (not "Core-2", as my first assumption).
Thanks for the other parameters though, I have never tried them. Gonna take
a look.
Francisco
