Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Date: Thu, 9 Dec 1999 00:40:10 -0500
From: Chris Faylor <cgf AT cygnus DOT com>
To: Mumit Khan <khan AT nanotech DOT wisc DOT edu>
Cc: Corinna Vinschen <corinna AT vinschen DOT de>,
        cygdev <cygwin-developers AT sourceware DOT cygnus DOT com>
Subject: Re: snapshot-991207
Message-ID: <19991209004009.A16999@cygnus.com>
Mail-Followup-To: Mumit Khan <khan AT nanotech DOT wisc DOT edu>,
	Corinna Vinschen <corinna AT vinschen DOT de>,
	cygdev <cygwin-developers AT sourceware DOT cygnus DOT com>
References: <19991208232235 DOT A16604 AT cygnus DOT com> <199912090512 DOT XAA16342 AT mercury DOT xraylith DOT wisc DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <199912090512.XAA16342@mercury.xraylith.wisc.edu>; from khan@nanotech.wisc.edu on Wed, Dec 08, 1999 at 11:12:50PM -0600

On Wed, Dec 08, 1999 at 11:12:50PM -0600, Mumit Khan wrote:
>I believe that the quoting in the snapshot I picked up last night was
>wrong, but didn't pay that much attention as to why.

I don't know what you mean by "wrong" but the version output looked ok
on Windows.  I assume that if windres could handle it, that it
must be "right" for my version of windres.

>The new signalling code seems to be doing just fine, and it's fixed
>one ``randomly hanging'' problem I was having with one of my tools.
>However, I notice make hanging indefinitely on Win98 after running
>so many jobs, and I have to kill -9 to kill it.

Well, if it's hanging, that's not a symptom of the signal code doing
fine.  If you can track down where it is hanging that will help me
figure out why.  I've found that using gdb to attach to a running
process is invaluable for this.  You might have to wander through
cygwin's various threads to find out who's hanging, though.

>btw, did you get a chance to look at enabling-signals-for-dynload patch?
>
>> -winver.o version.cc: mkvers.sh include/cygwin/version.h winver.rc $(DLL_OFIL
>> ES)
>> +version.cc winver.o: winver_version
>> +	@/bin/true
>> +
>> +winver_version: mkvers.sh include/cygwin/version.h winver.rc $(DLL_OFILES)
>>  	@echo "Making version.cc";rm -f $@;\
>					^^^
>					version.cc
>>  	$(SHELL) ${word 1,$^} ${word 2,$^} ${word 3,$^} $(WINDRES) > $@
>                                                                    ^^^^
>								  version.cc
>Few typos there. Also, it has a few other problems -- eg., run make, 
>delete winver.o and re-run make. As it is now, winver_version is also
>not a "phony".

Actually, I eliminated the > about ten seconds after sending out
the patch.  I still missed the 'rm -f $@', though.  Thanks.

cgf