From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Gentoo is the best linux distro
Date: Wed, 12 Sep 2012 16:55:37 +0200 [thread overview]
Message-ID: <20120912165537.6df718d8@khamul.example.com> (raw)
In-Reply-To: <50509582.5080300@wonkology.org>
On Wed, 12 Sep 2012 16:00:34 +0200
Alex Schuster <wonko@wonkology.org> wrote:
> Michael Mol writes:
>
> > On Wed, Sep 12, 2012 at 9:33 AM, Neil Bothwick <neil@digimed.co.uk
> > <mailto:neil@digimed.co.uk>> wrote:
>
> > Instead we get, try USE="-*" :P
> >
> > "Try MAKEOPTS='-j1'"
>
> Which in fact often helps... especially for me, I am using
> MAKEOPTS="-j --load=4", and I often experience build problems that
> are not reproducible with a fixed number of jobs, regardless how
> large.
Yes indeed, and that one is good advice.
Not every Makefile out there is safe for -j > 1, so running it as one
job is valid debugging. It's the correct thing to do with weird build
failures as it tests if a specific condition is true or not.
>
> > "Turn off distcc"
>
> "revdep-rebuild"
>
> And "emerge -e world && perl-cleaner --all && python-updater &&
> lafilefixer --justfixit".
Another example of proper debugging. A wise troubleshooter will first
verify that all relevant maintenance and consistency factors have been
done first before doing extensive troubleshooting.
The last one, "lafilefixer --justfixit" is especially valuable as it
gets right of a huge gigantic steaming pile of crap that a) should
never have been there at all in the first place and b) if it's causing
the problem is almost impossible to pin down without lots of work. So
even if b) is not true, you still get the huge benefit of a)
--
Alan McKinnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2012-09-12 15:01 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 21:46 [gentoo-user] Gentoo is the best linux distro Chris Stankevitz
2012-09-10 22:02 ` Dale
2012-09-10 22:12 ` Alan McKinnon
2012-09-11 0:41 ` Chris Stankevitz
2012-09-11 10:20 ` [gentoo-user] " Nikos Chantziaras
2012-09-12 1:45 ` Pandu Poluan
2012-09-10 22:24 ` [gentoo-user] " G.Wolfe Woodbury
2012-09-10 23:26 ` Paul Hartman
2012-09-11 2:56 ` Pandu Poluan
2012-09-11 9:43 ` Philip Webb
2012-09-12 10:03 ` Alan McKinnon
2012-09-12 13:33 ` Neil Bothwick
2012-09-12 13:47 ` Michael Mol
2012-09-12 14:00 ` Alex Schuster
2012-09-12 14:25 ` Michael Mol
2012-09-12 14:46 ` Neil Bothwick
2012-09-12 14:55 ` Alan McKinnon [this message]
2012-09-12 15:15 ` Michael Mol
2012-09-12 17:09 ` Joshua Murphy
2012-09-12 17:27 ` Michael Mol
2012-09-12 20:57 ` Alan McKinnon
2012-09-12 21:06 ` Michael Mol
2012-09-12 21:59 ` Paul Hartman
2012-09-12 22:08 ` Michael Mol
2012-09-12 22:40 ` Paul Hartman
2012-09-20 15:14 ` Daniel Wagener
2012-09-20 16:19 ` Dale
2012-09-20 18:39 ` Paul Hartman
2012-09-22 3:04 ` Allan Gottlieb
2012-09-12 17:46 ` Michael Hampicke
2012-09-12 17:56 ` Michael Mol
2012-09-12 13:55 ` Philip Webb
2012-09-12 14:49 ` Alan McKinnon
2012-09-12 20:06 ` Volker Armin Hemmann
2012-09-12 20:36 ` Mark Knecht
2012-09-12 22:01 ` Dale
2012-09-15 12:56 ` Graham Murray
2012-09-11 0:33 ` Mark Knecht
2012-09-12 8:24 ` Alan McKinnon
2012-09-12 8:47 ` Alex Schuster
2012-09-12 15:57 ` [gentoo-user] " Grant Edwards
2012-09-12 17:20 ` Dale
-- strict thread matches above, loose matches on Subject: below --
2012-09-11 7:14 [gentoo-user] " Cinder
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=20120912165537.6df718d8@khamul.example.com \
--to=alan.mckinnon@gmail.com \
--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