public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: jens.ohlund@secrc.abb.se
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] GCC and INSIGHT, snapshots
Date: Wed, 12 Jul 2000 23:29:00 -0000	[thread overview]
Message-ID: <OFF2097508.D7A846A7-ONC125691B.0022ED2B@secrc.abb.se> (raw)

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.
Neither of the egcs or insight completed the build (not very strange consideringthe above statement).
Config went through though.

Actually I'm just interested in a new version of Insight, since the inital release is a bit buggy/unstable
every now and then. AND it doesn't keep it's settings.

I building it for a ARM evaluation board, AEB-1, revision B.

yours
Jens





ecos-discuss-owner@sources.redhat.com
2000-07-13 08:19


To:   jens.ohlund@secrc.abb.se
cc:   ecos-discuss@sources.redhat.com
Subject:  Re: [ECOS] GCC and INSIGHT, snapshots

Security Level:?         Internal


jens.ohlund@secrc.abb.se wrote:
>
> It didn't work very well. I don't have the results (I tried last week) just didn't manage to make some patches and
> some it recognised as already done. this applies to both the ecos-gcc and the insight patch.
>
> If i got some time over a night or two I'll try again and give you the exact results. That is, IF you want them.

Perhaps it would be quicker for you if you just let me know:

- your host and target
- exactly which patches you are using
- exactly what source versions you are using (if any of them are snapshots,
then from about when)

I may be able to give you a quick answer or quick fix.

Thanks,

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





             reply	other threads:[~2000-07-12 23:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-12 23:29 jens.ohlund [this message]
2000-07-12 23:38 ` Jonathan Larmour
  -- 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=OFF2097508.D7A846A7-ONC125691B.0022ED2B@secrc.abb.se \
    --to=jens.ohlund@secrc.abb.se \
    --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).