Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Tue, 15 May 2001 17:37:24 EDT
To: Cygwin Developers <cygwin-developers AT cygwin DOT com>
Subject: Re: What is  dtable
X-Mailer: Virtual Access by Atlantic Coast PLC, http://www.atlantic-coast.com/va
Message-Id: <VA.00000773.01cb59d3@thesoftwaresource.com>
From: Brian Keener <bkeener AT thesoftwaresource DOT com>
Reply-To: bkeener AT thesoftwaresource DOT com
In-Reply-To: <3B004261.9C5CC7A5@yahoo.com>
References: <VA DOT 0000076e DOT 01c0bdbf AT thesoftwaresource DOT com> <20010511220359 DOT B30801 AT redhat DOT com> <VA DOT 0000076f DOT 006d0385 AT thesoftwaresource DOT com> <3AFFDBB1 DOT 898203E2 AT yahoo DOT com> <VA DOT 00000771 DOT 00395a79 AT thesoftwaresource DOT com> <3B0012D3 DOT 2508BBE0 AT yahoo DOT com> <VA.00000772. <3B004261 DOT 9C5CC7A5 AT yahoo DOT com>

Earnie Boyd wrote:
> Wait, you're doing a configure prior to the make clean.  That could be
> the problem since the initial Cygwin makefile is a special make run that
> establishes the makefiles for the subdirectories.  You should try moving
> the `make clean' before the configure and see if that helps.
>
That did it :-)  Moving the make clean before the configure did the trick. 
I did it again both ways just to be sure and sure enough - make clean 
after the configure in the script does not remove all it should but when 
placed before the configure it removed all of the build for cygwin, 
cinstall and so on just as it should.  

I noticed that when configure is run it changes the date on the makefile 
and wondered if that might be part of it.  Doesn't make do some date 
checking and so if the make clean is run after the configure changed the 
date on the makefile that might cause some bad date comparisons and thus 
some objects not get removed.  Ooorrrr, it could just be that configure 
changes the make file enough that make clean doesn't know what all to 
clean - which I think is sort of want you might have been inferring.

Thanks for the help Earnie.

bk