Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 25 Sep 2003 12:21:31 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: gcc -mno-cygwin fails Message-ID: <20030925162131.GA19510@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20030925143917 DOT GA2016 AT partners DOT org> <115190990369 DOT 20030925170940 AT familiehaase DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <115190990369.20030925170940@familiehaase.de> User-Agent: Mutt/1.4.1i On Thu, Sep 25, 2003 at 05:09:40PM +0200, Gerrit P. Haase wrote: >Gregory schrieb: > > >> Following up with recent problems noted about g77 -mno-cygwin, >> the same problem occurs for gcc. > >> I am using the newest packages: gcc-3.3.1-2, gcc-mingw-20030911-2 > >> $ gcc foo.c >> $ gcc -mno-cygwin foo.c >> gcc: installation problem, cannot exec `cc1': No such file or directory >> $ > >Make some symlinks in the directory: >/usr/lib/gcc-lib/i686-pc-mingw/3.3.1/ >to all the executables in this directory: >/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/ PLEASE DO NOT DO THIS! If there is a problem in the packaging then we fix the packaging. We don't give advice on how to work around the packaging. Cheesh. In this case, it seems like the gcc-mingw package wasn't actually installed. If standard problem reporting procedures had been employed (attaching cygcheck output), we would know this for sure. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/