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 sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com X-Apparently-From: Message-ID: <3A59D593.32643717@yahoo.com> Date: Mon, 08 Jan 2001 09:58:27 -0500 From: Earnie Boyd Reply-To: cygwin AT cygwin DOT com X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: "Charles S. Wilson" CC: cygwin AT sources DOT redhat DOT com Subject: Re: perl-5.6.1 DB_file support References: <3A5605B3 DOT AAC25D7F AT sbox DOT tu-graz DOT ac DOT at> <3A59255F DOT 85918DE8 AT sbox DOT tu-graz DOT ac DOT at> <3A5966E5 DOT 735999FE AT ece DOT gatech DOT edu> <3A59C529 DOT 4342E4D4 AT yahoo DOT com> <3A59CEBF DOT FFC6B476 AT ece DOT gatech DOT edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "Charles S. Wilson" wrote: > > Earnie Boyd wrote: > > > > "Charles S. Wilson" wrote: > > > #if defined(_WIN32) || defined(__CYGWIN__) > > > > > > To accommodate *bad* ports, cygwin's gcc used to define _WIN32, but that > > > behavior will be dropped soon IIRC. > > > > Where did you get that piece of information or are you dreaming? > > Although I would wholeheartedly support such a move, I don't think that > > the Cygwin's commercial client list would be that happy about such a > > move. > > That was my recollection of comments made on the list several months ago > (perhaps even a far as a year? Maybe even pre-departure-of-Mumit). > Basically, that "Eventually we want to do X..." kinda thing. This > 'vague recollection' has been reinforced by several recent emails from > you, Earnie, where you recommended using '-mno-win32'. I assummed that > was because the change I vaguely recalled would soon go into effect. > > Perhaps I misinterpreted, and your advice about '-mno-win32' was in > response to the defeat of the notion to remove '-D_WIN32' from the > cygwin gcc specs. > As I said, I would support wholeheartedly such a change, however Chris Faylor and Red Hat would have the final say. I do think that the WIN32 definitions get in the way of porting UNIX code to Cygwin especially when Win32 porting is already existing in the code. I do modify my own specs file to exclude the WIN32 defines by default and change the -mno-win32 to -mwin32 however with gcc-2.95.2-6 I had to binary edit cc1.exe (or was it cpp.exe) to complete this. Cheers, Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple