Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Fri, 19 Oct 2001 10:29:10 -0500
From: Grant Edwards <grante AT visi DOT com>
To: bgat AT billgatliff DOT com
Cc: cygwin AT sources DOT redhat DOT com, gdb AT sources DOT redhat DOT com
Subject: Re: [1.3.3] breaks serial i/o?
Message-ID: <20011019102909.A21982@visi.com>
References: <20011018161003 DOT A3059 AT saturn DOT billgatliff DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <20011018161003.A3059@saturn.billgatliff.com>; from bgat@saturn.billgatliff.com on Thu, Oct 18, 2001 at 04:10:03PM -0500

On Thu, Oct 18, 2001 at 04:10:03PM -0500, William A. Gatliff wrote:

> At this point, I would be happy just to be able to get Cygwin
> 1.3.2 back, but alas, I haven't found an archive of it anywhere
> on the 'net.

I've got a Cygwin source distro snapshot from a few months back
that we're distributing to our customers (along with arm-elf
toolchain) so they can do arm-elf development for our hardware
platform.  I personally haven't done remote stuff under Cygwin,
but others tell me it works. If you like, I could mail you a
CD, or I could put it on my ftp site.  I don't have enough
space for the whole thing, so I'd have to put the "contrib"
packages up seperately after you've grabbed the other stuff.

> To make matters worse, a magazine article I'm writing that
> describes how to use Cygwin and GNU tools for arm-elf
> development is set to appear in in the December issue of
> Circuit Cellar Ink magazine.  The article was written for
> 1.3.2, and won't currently work with 1.3.3 unless I can figure
> out what's going on by next Wednesday.  I really would rather
> avoid disappointing a new crop of Cygwin and GNU tool users.
> 
> I'm developing patches for gdb-5.0, binutils-2.11.2 and
> gcc-2.95.3 to make them build under 1.3.3 (to fix the new
> export conflicts), but I haven't figured out what the problem
> with serial communications is. If I can't fix the problem, then
> the article is basically doa.

That's too bad.  Cygwin has had serial problems in the past,
and I remember people having to install specific Cygwin
versions to get serial ports to work under gdb (and I presume
other apps as well).

> A draft of the manuscript for the article is at:
> 
> http://billgatliff.com/articles/gnu/gnu-arm7t/index.html.
> 
> Suggestions, patches, signs of moral support, etc. would all be
> most graciously accepted.  Thanks for the help,

-- 
Grant Edwards
grante AT visi DOT com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/