This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: bz2lib autoconfiguration ??
- To: Robert Collins <robert dot collins at itdomain dot com dot au>
- Subject: Re: bz2lib autoconfiguration ??
- From: Earnie Boyd <earnie_boyd at yahoo dot com>
- Date: Thu, 19 Apr 2001 07:43:46 -0400
- CC: Cygwin Developers <cygwin-developers at cygwin dot com>
- References: <EA18B9FA0FE4194AA2B4CDB91F73C0EF79C3@itdomain002.itdomain.net.au>
- Reply-To: Cygwin Developers <cygwin-developers at cygwin dot com>
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