| 1 |
On Thu, Oct 07, 2010 at 04:43:55AM +0200, meino.cramer@×××.de wrote |
| 2 |
|
| 3 |
> ================================================================= |
| 4 |
> System Settings |
| 5 |
> ================================================================= |
| 6 |
|
| 7 |
|
| 8 |
> CFLAGS="-march=amdfam10 -O2 -pipe -msse3" |
| 9 |
|
| 10 |
Let the compiler figure out the CPU. Change that line to... |
| 11 |
CFLAGS="-march=native -O2 -pipe" |
| 12 |
|
| 13 |
> CXXFLAGS="-march=amdfam10 -O2 -pipe -msse3" |
| 14 |
|
| 15 |
The recommended way of doing things here is... |
| 16 |
|
| 17 |
CXXFLAGS="${CFLAGS}" |
| 18 |
|
| 19 |
...which exactly copies whatever settings you have there. |
| 20 |
Synchronization between CFLAGS and CXXFLAGS becomes automatic this way. |
| 21 |
|
| 22 |
> MAKEOPTS="-j 12" |
| 23 |
|
| 24 |
Arrrrrrrrgh Nooooooooo!!! That's probably your problem right there. |
| 25 |
The recommendation in the manual is N+1, where N == number of cores. Do |
| 26 |
you have 11 or more cores? I find that even that isn't always safe. I |
| 27 |
set... |
| 28 |
|
| 29 |
MAKEOPTS="-j 1" |
| 30 |
|
| 31 |
and it solves quite a few problems. Note that the final binary is just |
| 32 |
as fast, regardless of that setting. The compile speed is somewhat |
| 33 |
faster with a higher number. But you quickly lose any "time savings" |
| 34 |
from that, the first time you waste several hours trying to figure out |
| 35 |
why something isn't compiling. MAKEOPTS="-j 1" should be mandatory. |
| 36 |
|
| 37 |
-- |
| 38 |
Walter Dnes <waltdnes@××××××××.org> |
Archives