From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] seq24 fails to comoile
Date: Thu, 7 Oct 2010 01:27:40 -0400 [thread overview]
Message-ID: <20101007052740.GB17511@waltdnes.org> (raw)
In-Reply-To: <20101007024354.GA5624@solfire>
On Thu, Oct 07, 2010 at 04:43:55AM +0200, meino.cramer@gmx.de wrote
> =================================================================
> System Settings
> =================================================================
> CFLAGS="-march=amdfam10 -O2 -pipe -msse3"
Let the compiler figure out the CPU. Change that line to...
CFLAGS="-march=native -O2 -pipe"
> CXXFLAGS="-march=amdfam10 -O2 -pipe -msse3"
The recommended way of doing things here is...
CXXFLAGS="${CFLAGS}"
...which exactly copies whatever settings you have there.
Synchronization between CFLAGS and CXXFLAGS becomes automatic this way.
> MAKEOPTS="-j 12"
Arrrrrrrrgh Nooooooooo!!! That's probably your problem right there.
The recommendation in the manual is N+1, where N == number of cores. Do
you have 11 or more cores? I find that even that isn't always safe. I
set...
MAKEOPTS="-j 1"
and it solves quite a few problems. Note that the final binary is just
as fast, regardless of that setting. The compile speed is somewhat
faster with a higher number. But you quickly lose any "time savings"
from that, the first time you waste several hours trying to figure out
why something isn't compiling. MAKEOPTS="-j 1" should be mandatory.
--
Walter Dnes <waltdnes@waltdnes.org>
next prev parent reply other threads:[~2010-10-07 5:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 2:43 [gentoo-user] seq24 fails to comoile meino.cramer
2010-10-07 5:27 ` Walter Dnes [this message]
2010-10-07 5:40 ` meino.cramer
2010-10-07 8:38 ` Arttu V.
2010-10-07 9:15 ` Stroller
2010-10-07 10:01 ` meino.cramer
2010-10-07 11:26 ` Alan McKinnon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101007052740.GB17511@waltdnes.org \
--to=waltdnes@waltdnes.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox