From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] wxGTK compilation fails "missing thread.h"
Date: Fri, 25 Jul 2014 21:33:24 +0100 [thread overview]
Message-ID: <20140725213324.464e58cb@hactar.digimed.co.uk> (raw)
In-Reply-To: <CALxYTP7gz-hP4oChOnC3hdk_56CwEbdP6OseYULyLYk-4XpXHw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
On Fri, 25 Jul 2014 09:38:50 -0700, Douglas J Hunley wrote:
> > I sometimes find this error coming from multi-thread compilation. I
> > fix it by
> > prepending the emerge command with MAKEOPTS="-j1". You could try that.
> >
>
> Indeed, this is probably parallelism gone wrong. However, you should
> really use package.env to override MAKEOPTS instead of using "one off"
> command line overrides
The one off override proves the need for the altered MAKEOPTS and
provides the ammunition for a bug report. Any ebuild that needs MAKEOPTS
to be overridden in package.env is buggy and should be reported as such.
--
Neil Bothwick
Dream as if you'll live forever. Live as if you'll die today.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2014-07-25 20:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 5:38 [gentoo-user] wxGTK compilation fails "missing thread.h" Adam Carter
2014-07-25 7:48 ` Peter Humphrey
2014-07-25 16:38 ` Douglas J Hunley
2014-07-25 20:33 ` Neil Bothwick [this message]
2014-07-25 21:32 ` Peter Humphrey
2014-07-26 10:47 ` Adam Carter
2014-07-26 11:43 ` Alexander Kapshuk
2014-07-26 11:59 ` Fwd: " Alexander Kapshuk
2014-07-27 9:30 ` Adam Carter
2014-07-27 12:18 ` Alexander Kapshuk
2014-07-28 1:33 ` Adam Carter
2014-07-28 5:16 ` Alexander Kapshuk
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=20140725213324.464e58cb@hactar.digimed.co.uk \
--to=neil@digimed.co.uk \
--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