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 sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: Eliminating usr/i686-pc-cygwin References: <20000606223406 DOT A3865 AT cygnus DOT com> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII From: Kazuhiro Fujieda Date: 08 Jun 2000 22:51:24 +0900 In-Reply-To: Chris Faylor's message of Tue, 6 Jun 2000 22:34:06 -0400 Message-ID: Lines: 19 X-Mailer: Gnus v5.3/Emacs 19.34 >>> On Tue, 6 Jun 2000 22:34:06 -0400 >>> Chris Faylor said: > 1) Setup.exe can issue a warning if it sees this directory, and do nothing. > 2) Setup.exe can issue a warning, and move the directory out of the way. > 3) Setup.exe can issue a warning, and remove the directory. > 4) Setup.exe can do 2) or 3) and do a: 'ln -s usr i686-pc-cygwin'. 5) Setup.exe can issue a warning; move such files as include/{_G_config.h,termcap.h}, include/X11/*, and lib/termcap.a into /usr; and then remove the directory. I like solution 3. These files, however, are lost by simply applying this solution. Then we should repackage gdb, termcap, and gcc without usr/i686-pc-cygwin. ____ | AIST Kazuhiro Fujieda | HOKURIKU School of Information Science o_/ 1990 Japan Advanced Institute of Science and Technology