From: Brian Drummond <brian@shapes.demon.co.uk>
To: gcc-help@gcc.gnu.org
Subject: Re: Problem with ARM cross compiler
Date: Thu, 19 Dec 2013 09:23:00 -0000 [thread overview]
Message-ID: <1387445030.3463.26.camel@Gannet.Four> (raw)
In-Reply-To: <52B2AB3A.3030501@wippies.com>
On Thu, 2013-12-19 at 10:15 +0200, Kai Ruottu wrote:
> 19.12.2013 2:15, Maxim Kuvyrkov kirjoitti:
> > On 19/12/2013, at 7:59 am, Hendrik Greving<hendrik.greving.intel@gmail.com> wrote:
> >
> >> I am compiling (trying to) ARM cross compiler (on x86):
> >>
> >>
> > ...
> >> conftest.c:15:19: fatal error: stdio.h: No such file or directory
> >>
> >>
> >> Any help/hint appreciated,
> > You don't have cross-built C library installed. Building a cross toolchain from scratch is an intricate process, it is not building just the compiler, you also need bintutils, C library headers and C library itself.
>
> I have never fully understood why the "totally from scratch target" is
> the first many people are trying
> when there are existing targets for crosstoolchains. My own '$sysroot's
> for the 'arm*-linux-gnueabi'
> targets in my laptop are :
>
> host-arm-angstrom-linux-gnueabi:
> host-arm-cs2009-linux-gnueabi:
> host-arm-cs2011-linux-gnueabi:
and many others...
How many of those are comprehensive toolchains, and how many omit bits
of gcc, like Ada or Fortran for example?
- Brian
next prev parent reply other threads:[~2013-12-19 9:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 18:59 Hendrik Greving
2013-12-19 0:16 ` Maxim Kuvyrkov
2013-12-19 8:15 ` Kai Ruottu
2013-12-19 9:23 ` Brian Drummond [this message]
2013-12-19 9:53 ` Andrew Haley
2013-12-19 18:46 ` Hendrik Greving
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=1387445030.3463.26.camel@Gannet.Four \
--to=brian@shapes.demon.co.uk \
--cc=gcc-help@gcc.gnu.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).