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
X-Authentication-Warning:	hp2.xraylith.wisc.edu: khan owned process doing -bs
Date:	Sat, 8 Jan 2000 17:43:13 -0600 (CST)
From:	Mumit Khan <khan AT NanoTech DOT Wisc DOT EDU>
To:	Chris Faylor <cgf AT cygnus DOT com>
cc:	Corinna Vinschen <corinna AT vinschen DOT de>,
	cygdev <cygwin-developers AT sourceware DOT cygnus DOT com>
Subject:	Re: ntsec-patch16 (and some other)
In-Reply-To:	<20000108182116.A1767@cygnus.com>
Message-ID:	<Pine.HPP.3.96.1000108173941.11094B-100000@hp2.xraylith.wisc.edu>
MIME-Version:	1.0

On Sat, 8 Jan 2000, Chris Faylor wrote:

> >No, my fault, I haven't described it clearly. In mingw/Makefile and
> >also in mingw/Makefile.in is the line
> >
> >	SUBDIRS:=profile
> >
> >and from here the rule `subdirs' seem to call the `make all' in
> >the profile dir that failes. AFAICS the problem is that the failing
> >make in the profiles subdir forces the end of the complete hirarchical
> >make process. Maybe it's enough to ignore the result code?!?
> 
> Hmm.  This is another problem from building in the same directory
> as the sources.  That's why I don't see it.

Same here. I don't remember the last time I built development tools
in the source directory, and that results in these problems being
overlooked. Note that gcc folks now *insist* that you build in an
object directory just to avoid some of these issues.

> I'm going to consider mingw to be exclusively Mumit's domain from now
> on, so I'd like to wait to see how he fixes this.

I'll be able to run some tests this evening, and if not, definitely 
tomorrow. Let you know how it goes.

My plan for the future merges of mingw and w32api into Cygwin is to
merge only what's necessary, maintaining local changes to configure
and so on. That should help with the process, and once we document
it (should be just a few little things), it should be rote.

btw, I actually expected a whole slew of problems after the reorg, but 
Chris seems to have gotten to those before the first snapshot. Good 
work!

Regards,
Mumit

- Raw text -