Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
Date: Sun, 5 Dec 1999 01:42:45 +0100 (CET)
Message-Id: <199912050042.BAA09715@oranje.my.domain>
From: Marc van Woerkom <van.woerkom@netcologne.de>
To: cgf@cygnus.com
CC: cygwin@sourceware.cygnus.com
In-reply-to: <19991204162353.B1386@cygnus.com> (message from Chris Faylor on
	Sat, 4 Dec 1999 16:23:53 -0500)
Subject: Re: ANN: das blinkenlights 0.0.1 cygwin distro
Reply-to: van.woerkom@netcologne.de
References: <199912022217.XAA01697@oranje.my.domain> <19991202212622.A7363@cygnus.com> <199912041830.TAA02960@oranje.my.domain> <19991204162353.B1386@cygnus.com>

> >Turned out that this is not as easy as I thought. 
> 
> How is downloading the winsup/newlib sources difficult?

The difficulity is getting sure that one has a rather recent
version before ones eyes.

In my case it is about one of the tools, objdump to be precise.
As far as I know, the public source archives are about a year old. 
So the question is, where patches would go.
Quite likely people would mail them to the dev lists.

This leaves searching the archives, searching the site for
interim releases or asking the maintainers.

The easy way I thought of was locating the tree on the web site,
have a short look at the objdump sources and to bugger off.

Regards,
Marc


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com