From: Adam Carter <adamcarter3@gmail.com>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] wxGTK compilation fails "missing thread.h"
Date: Sat, 26 Jul 2014 20:47:12 +1000 [thread overview]
Message-ID: <CAC=wYCHjSRzf4BhaNuj-tjr9XTRoobmm7X4HS5dRw1nN9m_EiA@mail.gmail.com> (raw)
In-Reply-To: <3577137.OUgBVV6bEF@wstn>
[-- Attachment #1: Type: text/plain, Size: 976 bytes --]
On Fri, Jul 25, 2014 at 5:48 PM, Peter Humphrey <peter@prh.myzen.co.uk>
wrote:
> On Wednesday 23 July 2014 15:38:42 Adam Carter wrote:
> > Here's what i get;
> >
> /var/tmp/portage/x11-libs/wxGTK-2.8.12.1-r1/work/wxPython-src-2.8.12.1/src/u
> > nix/threadpsx.cpp:51:24: fatal error: thread.h: No such file or directory
> > make: *** [basedll_threadpsx.o] Error 1
> >
> > Any ideas? Would thread.h be supplied by another package? linux-headers
> > doesnt have it.
>
> 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.
>
>
I always try -j1 when anything fails to avoid troubling the list, however
it didnt help in this case. Did you suspect that thread.h is generated by
the package build process, or is there some other reason why parallel build
could cause this problem? AFAIK header files are not generated. I would
have guessed its a path problem or missing dependency.
[-- Attachment #2: Type: text/html, Size: 1401 bytes --]
next prev parent reply other threads:[~2014-07-26 10:47 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
2014-07-25 21:32 ` Peter Humphrey
2014-07-26 10:47 ` Adam Carter [this message]
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='CAC=wYCHjSRzf4BhaNuj-tjr9XTRoobmm7X4HS5dRw1nN9m_EiA@mail.gmail.com' \
--to=adamcarter3@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