From: Grant Edwards <grante@visi.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: Problems with ecosconfig
Date: Wed, 31 May 2006 20:12:00 -0000 [thread overview]
Message-ID: <20060531201250.1CEA7542DF@rivatek.dnsalias.net> (raw)
In-Reply-To: <20060531183726.GF6189@lunn.ch>
>> This is my first posting. I am beginner in eCos. Sorry, my
>> english is badly (I am from Russia). I am trying to install
>> eCos-1.3.1. After installing GNU Toolchain
>
> 1.3.1! That is something like 6 years old. I suggest you
> update to anoncvs.
There are some particularly tricky bugs in the 1.3.1 network
stack. I definitely recommend not using 1.3.1 in network
applications.
--
Grant Edwards grante Yow! If you STAY in China,
at I'll give you 4,000 BUSHELS
visi.com of "ATOMIC MOUSE" pencil
sharpeners!!
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2006-05-31 20:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 18:02 [ECOS] " Денис Шевченко
2006-05-31 18:37 ` Andrew Lunn
2006-05-31 20:12 ` Grant Edwards [this message]
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=20060531201250.1CEA7542DF@rivatek.dnsalias.net \
--to=grante@visi.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).