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: Wed, 22 Oct 2003 13:58:26 +0200 From: "Gerrit P. Haase" Reply-To: "Gerrit P. Haase" Organization: Esse keine toten Tiere X-Priority: 3 (Normal) Message-ID: <1861820771741.20031022135826@familiehaase.de> To: "Demmer, Thomas" CC: "'cygwin AT cygwin DOT com'" Subject: Re: Slight gcc -mno-cygwin inconsistency In-Reply-To: <8D861ADC5B8FD211B4100008C71EA7DA04F71253@kjsdemucshrexc1.eu.pm.com> References: <8D861ADC5B8FD211B4100008C71EA7DA04F71253 AT kjsdemucshrexc1 DOT eu DOT pm DOT com> MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Thomas schrieb: > Well, > so far everything I installed was consistent in terms of > header files between cygwin and mingw, so, yes until now I > do want mingw to search in /usr/include. But I see your > point and maybe I was just lucky (I do not want the linker > to search in /usr/local/lib, though). But it is pretty useless to have a function declared in a Cygwin header which is exported from cygwin1.dll in a MinGW application since the linker doesn't link against libcygwin.a. You can do this as long as the functions are identical, but what for? If this function is available for MinGW then there is also a MinGW header declaring this function. If the function() is not available for MinGW, then your application will not link anyway. 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/