public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: "Moore, Richard F." <rfm6@leicester.ac.uk>
To: "crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: fatal error: pthread.h: No such file or directory
Date: Mon, 14 Mar 2016 15:54:00 -0000	[thread overview]
Message-ID: <1457970862.30814.23.camel@le.ac.uk> (raw)

Hi Yann,

Pulling latest git, I make, then do this to use built in recipe

./ct-ng x86_64-unknown-linux-uclibc

Everything builds fine.


If I do the same but only change (via ct-ng menuconfig) the target to
be 32 bit rather than 64 bit I get this on pass-2;


[INFO ]  Installing C library headers: done in 6.68s (at 08:20)
[INFO ] 
 =================================================================
[INFO ]  Installing pass-2 core C gcc compiler
[EXTRA]    Configuring core C gcc compiler
[EXTRA]    Building gcc
[ERROR]    /media/3/cyclone/crosstool-ng/.build/src/gcc
-5.3.0/libgcc/generic-morestack-thread.c:41:21: fatal error: pthread.h:
No such file or directory
[ERROR]    make[2]: *** [generic-morestack-thread.o] Error 1
[ERROR]    make[1]: *** [all-target-libgcc] Error 2
[ERROR]   
[ERROR]  >>
[ERROR]  >>  Build failed in step 'Installing pass-2 core C gcc
compiler'
[ERROR]  >>        called in step '(top-level)'
[ERROR]  >>
[ERROR]  >>  Error happened in: CT_DoExecLog[scripts/functions@259]
[ERROR]  >>        called from: do_gcc_core_backend[
scripts/build/cc/100-gcc.sh@520]
[ERROR]  >>        called from: do_gcc_core_pass_2[
scripts/build/cc/100-gcc.sh@154]
[ERROR]  >>        called from: do_cc_core_pass_2[
scripts/build/cc.sh@42]
[ERROR]  >>        called from: main[scripts/crosstool-NG.sh@650]
[ERROR]  >>
[ERROR]  >>  For more info on this error, look at the file: 'build.log'
[ERROR]  >>  There is a list of known issues, some with workarounds,
in:
[ERROR]  >>      'share/doc/crosstool-ng/crosstool-ng-1.22.0-126
-gd7339f5/B - Known issues.txt'
[ERROR]   
[ERROR]  (elapsed: 12:13.06)
[12:13] / ct-ng:152: recipe for target 'build' failed
make: *** [build] Error 2


I have tried altering various versions of build tools and it is always
the same error.
(I tried attaching build.log but it just bounced so resending without)


Cheers

Rich

             reply	other threads:[~2016-03-14 15:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14 15:54 Moore, Richard F. [this message]
2016-03-14 16:04 ` Waldemar Brodkorb
2017-02-23 20:54 Marc-Antoine Martin
2017-02-23 21:12 ` Alexey Neyman

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=1457970862.30814.23.camel@le.ac.uk \
    --to=rfm6@leicester.ac.uk \
    --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).