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: Thu, 19 Apr 2001 08:04:27 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: Cygwin Developers <cygwin-developers AT cygwin DOT com>
Subject: Re: bz2lib autoconfiguration ??
Message-ID: <20010419080427.A19483@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: Cygwin Developers <cygwin-developers AT cygwin DOT com>
References: <EA18B9FA0FE4194AA2B4CDB91F73C0EF79C3 AT itdomain002 DOT itdomain DOT net DOT au> <3ADECF72 DOT 4191C20F AT yahoo DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <3ADECF72.4191C20F@yahoo.com>; from earnie_boyd@yahoo.com on Thu, Apr 19, 2001 at 07:43:46AM -0400

On Thu, Apr 19, 2001 at 07:43:46AM -0400, Earnie Boyd wrote:
>Robert Collins wrote:
>> 
>> AFAIK it's by design.
>> 
>> Adding new subdirs with separate packages typically involves a new
>> distribution.
>> 
>> The --norecurse is to prevent changes to configure.[in|ac] at the top of
>> a set of related packages forcing reconfiguration for the sub-packages.
>> This has the side effect of not configuring added packages.
>> 
>
>Hmm...  Ok, so I decided to try ./config.status --recheck --recurse in
>the i686-pc-cygwin/winsup directory.  That didn't help.

Since --recurse is not an option to config.status, I'm not surprised.

>Also executing configure in the top build directory will remove all
>configuration files from the i686-pc-cygwin/winsup directory.  :0

It will recreate the config.status and config.h files in the winsup
hierarchy.

>The way things are setup the only solution for obtaining configuration
>in a new subdirectory is to execute ../src/configure.  Perhaps the top
>level Makefile should reexecute configure instead of `config.status
>--recheck'??  Or the top level config.status should be made to remove
>the winsup configuration files from the winsup subdir?

Since adding new directories to the winsup directory is a relatively
rare event and since winsup's makefile is similar to the rest of the
build tree, I don't think there is any reason to change.

cgf