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:15:00 -0000 [thread overview]
Message-ID: <OF8CE6B591.29F554A4-ONC125691B.0021FBC4@secrc.abb.se> (raw)
Hi !
that one I can answer on at once :)
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.
yours
Jens
ecos-discuss-owner@sources.redhat.com
2000-07-13 08:00
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:
>
> Hi !
>
> Lets see if I understood you right :)
>
> For time beeing I DON'T have to patch the latest gcc/insight snapshots, just build them and go ?
Not really :-). In summary, if the installation instructions tell you to
apply some patches, apply them. If you have problems applying them, come
back here and tell us.
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 reply other threads:[~2000-07-12 23:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-12 23:15 jens.ohlund [this message]
2000-07-12 23:19 ` 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:29 jens.ohlund
2000-07-12 23:38 ` 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=OF8CE6B591.29F554A4-ONC125691B.0021FBC4@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).