From: Jonathan Larmour <jlarmour@redhat.co.uk>
To: jens.ohlund@secrc.abb.se
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] GCC and INSIGHT, snapshots
Date: Thu, 13 Jul 2000 08:00:00 -0000 [thread overview]
Message-ID: <396DD981.60DFB945@redhat.co.uk> (raw)
In-Reply-To: <OF90B42591.9D6A01A5-ONC125691B.003B1BE5@secrc.abb.se>
jens.ohlund@secrc.abb.se wrote:
>
> Hi !
>
> Well , i just followed the links from the eCos page.
>
> Lets see now...
> gcc:
> ftp://gcc.gnu.org/pub/gcc/snapshots/index.html
>
> insight:
> ftp://sourceware.cygnus.com/pub/gdb/snapshots/
> It got snapshots both for gcb and insight.
You shouldn't use snapshots unless you need to. Just follow the
instructions on the web page and it will tell you what to use, and what
patches to apply. Only deviate from that if you know what you are doing!
Snapshots are less stable than the stable released versions. In other
words, where possible, use binutils 2.10, gcc 2.95.2 and gdb/insight 5.0.
But the instructions will tell you this.
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-13 8:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-13 3:52 jens.ohlund
2000-07-13 8:00 ` Jonathan Larmour [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-13 3:08 danish iftikhar
2000-07-12 23:29 jens.ohlund
2000-07-12 23:38 ` Jonathan Larmour
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=396DD981.60DFB945@redhat.co.uk \
--to=jlarmour@redhat.co.uk \
--cc=ecos-discuss@sourceware.cygnus.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).