public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.co.uk>
To: "amassa@cts.com" <amassa@cts.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] Re: New Release
Date: Wed, 31 May 2000 10:03:00 -0000	[thread overview]
Message-ID: <393545C0.AC0EFE0A@redhat.co.uk> (raw)
In-Reply-To: <200005311641.JAA07615@batman.cts.com>

"amassa@cts.com" wrote:
> 
> When I send email to ecos-discuss@sourceware.cygnus.com it always bounces
> back saying that it is not allowing my message to go through because it is
> trying to cut down on spam.  Do you know why this is happening.

That probably means that your site, or your ISPs site, are associated with
spam. Please read http://sourceware.cygnus.com/lists.html#orbs-sucks

> I have been having a tough time with the cygwin 1.1.1 release.  I tried to
> build eCos using the configuration tool, however, I get makefile errors.  Do
> you know what this could be?

Not if you don't say what the problems are! There is a bug in the current
eCos configuration tool where it does not mount the drives in text mode
correctly. To work around this, type in the following at a cygwin bash
prompt:

mount c:/ /c

You should do something similar for each drive (d: e: etc.) which is used
for eCos development, e.g.

mount d:/ /d

and so on.
 
> I saw in a previous post that a new release of cygwin (1.1.2) is coming out
> and I also see that there is a new insight (5.0) release.  Is is best to
> re-install everything cygwin, binutils, gcc and insight?

You should not need to reinstall cygwin when the upgrade comes out -
instead run "setup -u" and install from the internet which will upgrade
only those bits that need upgrading. Insight 5.0 is unlikely to give you
much benefit over the one you are using, if you only just installed a
recent snapshot. It is unlikely to be worth it, but obviously you can if
you want - there's nothing stopping you!

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-05-31 10:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200005311641.JAA07615@batman.cts.com>
2000-05-31 10:03 ` Jonathan Larmour [this message]
     [not found] <000001bfcb68$731b0090$0c0cbcc0@machine1dsktp.cts.com>
2000-06-01  8:14 ` Jonathan Larmour
     [not found] <200006011600.JAA59542@batman.cts.com>
2000-06-01  9:12 ` Jonathan Larmour
     [not found] <200006011622.JAA60914@batman.cts.com>
2000-06-01 13:06 ` 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=393545C0.AC0EFE0A@redhat.co.uk \
    --to=jlarmour@redhat.co.uk \
    --cc=amassa@cts.com \
    --cc=ecos-discuss@sourceware.cygnus.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).