Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com X-Apparently-From: Message-ID: <3ADECF72.4191C20F@yahoo.com> Date: Thu, 19 Apr 2001 07:43:46 -0400 From: Earnie Boyd Reply-To: Cygwin Developers X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Robert Collins CC: Cygwin Developers Subject: Re: bz2lib autoconfiguration ?? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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. Also executing configure in the top build directory will remove all configuration files from the i686-pc-cygwin/winsup directory. :0 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? Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com