From: Marc-Antoine Martin <martin.marcantoine@gmail.com>
To: crossgcc@sourceware.org
Subject: Re: fatal error: pthread.h: No such file or directory
Date: Thu, 23 Feb 2017 20:54:00 -0000 [thread overview]
Message-ID: <CAMafisb0kFHViGoNOLQzgEPwRfo0R0ktoh3uv72N330d82OtYQ@mail.gmail.com> (raw)
Hi all,
I bring this post back on top.
I'm currently trying to build a crosstool for x86 plateform with the
sample "x86_64-unknown-linux-uclibc"
Each time I compile it (whenever changes of the kconfig (bitness
apart)) I have the error "fatal error: pthread.h: No such file or
directory" on compilation of
"gcc-5.2.0/libgcc/generic-morestack-thread.c" (error:
http://pastebin.com/ESkQ68eD)
I've seen this post and the Waldemar suggest to use this patch (made
for buildroot): http://patchwork.ozlabs.org/patch/592962/
Did anyone test it or made an updated one for crosstool-ng?
Is it safe to use it without any changes?
I'm not used to build crosstools and apply patches, I'm still leaning.
Thank for your assistance.
Regards,
Marc-Antoine Martin
next reply other threads:[~2017-02-23 20:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 20:54 Marc-Antoine Martin [this message]
2017-02-23 21:12 ` Alexey Neyman
-- strict thread matches above, loose matches on Subject: below --
2016-03-14 15:54 Moore, Richard F.
2016-03-14 16:04 ` Waldemar Brodkorb
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=CAMafisb0kFHViGoNOLQzgEPwRfo0R0ktoh3uv72N330d82OtYQ@mail.gmail.com \
--to=martin.marcantoine@gmail.com \
--cc=crossgcc@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).