From: "Lewin A.R.W. Edwards" <larwe@larwe.com>
To: Rafael RodrÃÂguez Velilla <rrv@tid.es>,
ecos <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] ARM Thumb
Date: Fri, 27 Apr 2001 05:44:00 -0000 [thread overview]
Message-ID: <4.3.2.7.2.20010427083823.033d5810@mail.larwe.com> (raw)
In-Reply-To: <3AE91DA8.EC024FF1@tid.es>
> When I build the toolchain for eCos I follow the indications of eCos'
> web page.
>In there they use the switch --with-newlib, but I have never built newlib
>itself.
> Is the output of newlib the library libgcc.a?
You can get newlib by following the "other projects" (or is it "more
projects"?) link on sources.redhat.com. Note that this is yet another piece
of software that seems broken on cygwin. I had to build it on a Linux
system and move it across.
If you build newlib 1.9.0 with a recent cvs snapshot of gcc then you'll get
both the arm and thumb versions of the library (libc.a, libm.a,
thumb/libc.a, thumb/libm.a) built automatically.
=== Lewin A.R.W. Edwards (Embedded Engineer)
Work: http://www.digi-frame.com/
Personal: http://www.zws.com/ and http://www.larwe.com/
"... a man who is endowed with real qualities of leadership will be tempted
to refrain from taking part in political life; because [...] the situation
does not call for a man who has a capacity for constructive statesmanship
but rather for a man who is capable of bargaining for the favour of the
majority. Thus the situation will appeal to small minds and will attract
them accordingly."
next prev parent reply other threads:[~2001-04-27 5:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-26 9:21 Roman
2001-04-26 10:31 ` Lewin A.R.W. Edwards
2001-04-26 12:23 ` Jonathan Larmour
2001-04-26 12:30 ` Lewin A.R.W. Edwards
2001-04-30 9:18 ` Rafael RodrÃguez Velilla
2001-04-30 11:58 ` Jonathan Larmour
2001-04-27 0:43 ` Rafael RodrÃguez Velilla
2001-04-27 5:44 ` Lewin A.R.W. Edwards [this message]
2001-04-27 3:03 ` [ECOS] using struct II Carlos Camargo
2001-04-26 11:11 ` [ECOS] ARM Thumb 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=4.3.2.7.2.20010427083823.033d5810@mail.larwe.com \
--to=larwe@larwe.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=rrv@tid.es \
/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).