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
Date: Wed, 26 Jan 2000 16:03:04 -0500
Message-Id: <200001262103.QAA22652@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: cgf AT cygnus DOT com
CC: earnie_boyd AT yahoo DOT com, cygwin-developers AT sourceware DOT cygnus DOT com
In-reply-to: <20000126154352.A5426@cygnus.com> (message from Chris Faylor on
	Wed, 26 Jan 2000 15:43:52 -0500)
Subject: Re: next net release preliminary info
References: <20000126162956 DOT 4192 DOT qmail AT web111 DOT yahoomail DOT com> <200001262027 DOT PAA06771 AT envy DOT delorie DOT com> <20000126154352 DOT A5426 AT cygnus DOT com>


> Hmm.  When I hear dependencies, I think Makefile.

The problem I was thinking about was "build from source, oops wrong
version of readline, build fails."

> How about a "make install" for the binary packages?

Why?  Untarring them installs them into the right spot already.  I
don't think there are any real binary dependencies, just source
dependencies.  If we supported shared libraries, that would be a
different story, but everything is statically linked (except the
tcl/tk stuff, but gdb works without it anyway, with --nw).