Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 25 Sep 2003 17:21:56 +0200 From: "Gerrit P. Haase" Reply-To: "Gerrit P. Haase" Organization: Esse keine toten Tiere X-Priority: 3 (Normal) Message-ID: <42191726357.20030925172156@familiehaase.de> To: Igor Pechtchanski Subject: Re: g77 -mno-cygwin failed In-Reply-To: References: <3F72F57B.1CD0D20B@ecn.nl> <3F7305D3.9E276BFC@ecn.nl> MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Igor Pechtchanski wrote: >> There is a softlink missing in >> /usr/lib/gcc-lib/i686-pc-mingw32/3.3.1 and >> hence missing in gcc-mingw-3.3.1-20030804.tar >> Making this softlink from within this subdir fixes the problem: >> ln -s ../../i686-pc-cygwin/3.3.1/f771.exe f771.exe > No, no, no! This will produce an executable linked with Cygwin (as can be > verified by running "cygcheck" on it). You don't want that -- you want > MinGW executables to be regular Windows programs, using MSVCRT.DLL as > their C/Fortran runtime. Why? What are the -mno-cygwin flags good for then? This was also the way it was in gcc-3.2-x and it worked IIRC. Gerrit -- =^..^= -- 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/