public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Han Sooloo <hansooloo@gmail.com>
To: crossgcc@sourceware.org
Subject: i686-nptl-linux-gnu fails with lib-names.h not found message
Date: Mon, 25 Jun 2012 02:02:00 -0000	[thread overview]
Message-ID: <0E5745B6-BAFC-4A8C-8DB1-DBD59ED07DCB@gmail.com> (raw)

Hello all,

Trying to build tool chain on my Ubuntu 12.04, running inside a VMware Fusion 4 VM.  Target is i686-nptl-linux-gnu.  Using the following:
GCC 4.7.0, glibc 2.13, GMP 4.3.2, MPFR 2.4.2, PPL 0.11.2, CLoog/ppl 0.15.11, MPC 0.8.2.

I first copy the .config from samples directory: 'cp ../crosstool-ng-1.15.2/samples/i686-nptl-linux-gnu/crosstool.config ./.config'.  After that I do modifications to the config to match the versions above.

When I run 'ct-ng build', it fails at the "Installing C library headers & start files" step.  The error message (briefly) is as follows:
[ALL  ]    /usr/bin/install: cannot stat `/home/hansolo/x-tools/.build/i686-nptl-linux-gnu/build/build-libc-startfiles/gnu/lib-names.h': No such file or directory

Any thoughts on what could be causing this?


--
For unsubscribe information see http://sourceware.org/lists.html#faq

                 reply	other threads:[~2012-06-25  2:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=0E5745B6-BAFC-4A8C-8DB1-DBD59ED07DCB@gmail.com \
    --to=hansooloo@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).