Message-Id: <200006081819.OAA18987@delorie.com>
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
From: "Parker, Ron" <rdparker AT butlermfg DOT com>
To: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: RE: More i686-pc-cygwin woes.
Date: Thu, 8 Jun 2000 13:11:11 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="windows-1252"

> I force this to occur by specifying the regular "correct" stuff in
> configure and using a line like this for the 'make install':
> 
>         make tooldir=/usr install
> 
> This causes cygwin to avoid using i686-pc-cygwin directory.

Would it be better if we had our own version of autoconf that when it was
dealing with a cygwin target set tooldir appropriately?  And yes I am
volunteering.  

We could then autoconf the packages that referred to this directory and
release a new tar ball and source for those packages.  Also if a user had
complained of a third-party package that was errantly placing files in
/usr/i686-pc-cygwin, we could direct him to:

	autoconf
	./configure --prefix=/usr i686-pc-cygwin
	make
	make install

Which isn't that abnormal anyway.