X-Spam-Check-By: sourceware.org
Message-ID: <43A17093.DEA81765@dessent.net>
Date: Thu, 15 Dec 2005 05:33:07 -0800
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: CygWin + gcc to build Windows application written in C.
References: <000401c60165$0ff24c60$0300a8c0 AT Piero>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Piero Silvestri wrote:

> But then I downloaded the gcc 4.0.2 sources, which I compiled in Cygwin with
> the old gcc provided, so now I have a second version of gcc currently
> working. The problem is that this version has some problem with
> the -mno-cygwin option; if I use it when compiling I get the error message:
> "gcc: installation problem, cannot exec 'cc1': No such file or directory".
> Do you think that this is a CygWin's configuration problem or a gcc one?

In order for -mno-cygwin to work you essentially have to build gcc twice
(with --target=i686-pc-cygwin and then again with
--target=i686-pc-mingw32) and install them to the same tree.  That's why
it complains about not being able to find cc1.  If you're not using
--enable-version-specific-runtime-libs that will probably also be
required.  And I wouldn't be surprised if you had to do some patching of
the specs file in order to get it fully working.  This option is more of
a Cygwin-specific patch, I am not sure whether it is fully supported by
the upstream FSF sources.

To get an idea how it works, look at the current gcc specs file and
layout of the gcc and gcc-mingw packages, and their source tarballs.

But I don't understand why you're building a cygwin targeted gcc
yourself if you intend to always run in mingw mode - just build a mingw
gcc if that's what you want.

Brian

--
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/