Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Reply-To: From: "Norman Vine" To: Subject: RE: New version of setup.exe with fixes for i686-pc-cygwin/* problem Date: Thu, 8 Jun 2000 12:46:14 -0400 Message-ID: <000101bfd169$155dbfe0$ab37ba8c@nhv> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 Importance: Normal In-Reply-To: <20000608122952.A19550@cygnus.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Chris Faylor writes: >I've uploaded a new version of setup.exe to sourceware >which just deletes files in the i686-pc-cygwin hierarchy that >are outdated by the new cygwin 1.1.2 (or >any other installation, for that matter) installation. > Chris Just to make sure I am doing things right I also had to manually put _G_config.h into /usr/include So should I recreate the i686-pc-cygwin directory or is it OK to leave as is in / usr / include ?? Only other thing I have noticed is that some installs seem to leave headers in DOS form /r/n when installing them into / usr / local / include from a text mounted drive / is mounted as binary readline-4.0 and python-1.52 both did this This causes problems for gcc until I manually run the files through a d2U filter. Could this be due to my setup ?? NHV:/> mount Device Directory Type Flags c:\cygwin\bin /usr/bin user binmode c:\cygwin\lib /usr/lib user binmode c:\cygwin / user binmode c: /c user textmode d: /d user textmode e: /e user textmode f: /f user textmode Other then this V1.2 seems to work like a charm :-))) Many Thanks to all involved !! Norman VIne -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com