From: Jonathan Larmour <jlarmour@redhat.co.uk>
To: jens.ohlund@secrc.abb.se
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] GCC and INSIGHT, snapshots
Date: Wed, 12 Jul 2000 23:38:00 -0000 [thread overview]
Message-ID: <396D63D1.5EA412FE@redhat.co.uk> (raw)
In-Reply-To: <OFF2097508.D7A846A7-ONC125691B.0022ED2B@secrc.abb.se>
jens.ohlund@secrc.abb.se wrote:
>
> Hi !
>
> Hummm. I just followed the instructions on the eCos homepage.
>
> Binutils, the latest 2.10 release. Unpack and build, no probs.
> egcs, I just picked a daily build. Can't remember which one. Anyone is of interest.
> Same goes about Insight.
>
> I applied the patches from the homepage, ecos-gcc.2.95.2.pat and insight-5.0.pat.
> It whined when I applied the pacthes.
Ahhh... you are using snapshots for a target where we haven't recommended
snapshots. I assumed it was one of the targets we do. Okay, that's
different - the patches are for the releases given in their name (not very
surprisingly), not for the snapshots.
For the specific case of the arm-elf target you don't need any gcc or gdb
patches. You've got the answer you wanted - sorry it took so long :-).
Jifl
--
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow." || These opinions are all my own fault
next prev parent reply other threads:[~2000-07-12 23:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-12 23:29 jens.ohlund
2000-07-12 23:38 ` Jonathan Larmour [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-13 3:52 jens.ohlund
2000-07-13 8:00 ` Jonathan Larmour
2000-07-13 3:08 danish iftikhar
2000-07-12 23:15 jens.ohlund
2000-07-12 23:19 ` Jonathan Larmour
2000-07-12 22:57 jens.ohlund
2000-07-12 23:00 ` Jonathan Larmour
2000-07-05 8:10 jens.ohlund
2000-07-05 10:52 ` Bart Veer
2000-07-12 16: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=396D63D1.5EA412FE@redhat.co.uk \
--to=jlarmour@redhat.co.uk \
--cc=ecos-discuss@sources.redhat.com \
--cc=jens.ohlund@secrc.abb.se \
/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).