public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <jld@ecoscentric.com>
To: ecos-maintainers@ecos.sourceware.org
Cc: Berenyi Balazs <beba@koli.kando.hu>
Subject: Re: Problem with cygwin 1.5.* (newest) and gdb 5.3 (prebuild)
Date: Thu, 04 Dec 2003 10:44:00 -0000	[thread overview]
Message-ID: <3FCF101E.4070901@ecoscentric.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0312041032410.8666@drama.koli>

eCos maintainers

Berenyi Balazs wrote:

> I just started playing with GNU tools and Atmel EB40.
> 
> As you have writen i have installed cygwin and downloaded
> prebuild gnutools.
> 
> I wanted to upload redbood to the EB40, but it did not worked
> as you documented. I could not connect with GDB to Angel.
> 
> As i found this is becouse of some changes in Cygwin.
> 
> See more (and the patch for GDB) on :
> http://sources.redhat.com/ml/gdb/2003-09/msg00290.html
> There was some conversation about this problem.
> 
> Please make a note on your (very good) step-by-step tutorial
> to use an _older_cygwin_.
> 
> Please note that this is my first touch on GNU tools and my first
> error report.

The most significant implication is that Windows users using Cygwin 
1.5.x will be unable to perform an initial installation of RedBoot on 
Atmel AT91EB* boards. The Cygwin net installer still provides Cygwin 
1.3.22 but there are already Cygwin packages which require Cygwin 1.5.x 
so we cannot reasonably insist that eCos users stick with Cygwin 1.3.x.

I suggest that we add an appropriate arm-elf-gdb patch to the list of 
patches which should be applied when building an eCos toolchain.

John Dallaway
eCosCentric Limited

  reply	other threads:[~2003-12-04 10:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-04  9:48 Berenyi Balazs
2003-12-04 10:44 ` John Dallaway [this message]
2003-12-04 21:21   ` Berenyi Balazs

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=3FCF101E.4070901@ecoscentric.com \
    --to=jld@ecoscentric.com \
    --cc=beba@koli.kando.hu \
    --cc=ecos-maintainers@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).