From: "Igor Trevisan" <igor@bluewind.it>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Errors while cross compiling for ARM
Date: Tue, 07 Nov 2000 09:32:00 -0000 [thread overview]
Message-ID: <3A084694.28291.19B18B@localhost> (raw)
Hi.
I built an ARM-Thumb development tool for Linux following step
by step all the instructions I found in the page:
"Building the thumb-elf development tools for Linux",
but if I try to cross-compile a simple "hello.c" file I don't succeed
because of the fact that my arm-gcc doesn't find any include file;
in the present case it consider stdio.h as "not existent".
What can I do to avoid this problem?
Thanks in advance to everyone that will help me.
Igor.
---------------------------------------------------------
BlueWind Electronic Design
I-31033 Castelfranco Veneto (TREVISO)
Via Steffani 7/B
---------------------------------------------------------
VOICE +39 0 423 723431
FAX +39 0 423 744738
MOBILE +39 349 7787328
mailto:igor@bluewind.it
http://www.bluewind.it
-----------------------------------------
next reply other threads:[~2000-11-07 9:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-07 9:32 Igor Trevisan [this message]
2000-11-07 9:59 ` Jonathan Larmour
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=3A084694.28291.19B18B@localhost \
--to=igor@bluewind.it \
--cc=ecos-discuss@sources.redhat.com \
/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).