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 Message-ID: <3500515B75D9D311948800508BA37955014BD7A7@EX-LONDON> From: Vince Hoffman To: "'Gunnar DOT Ritter AT pluto DOT uni-freiburg DOT de'" , "'cygwin AT cygwin DOT com'" Subject: RE: Using nail on win32 (cygwin) Date: Fri, 17 Jan 2003 16:21:05 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" While i can understand your views, i'm sorry that you feel that way. thanks for the responce. Vince > -----Original Message----- > From: Gunnar Ritter [mailto:g-r AT bigfoot DOT de] > Sent: 17 January 2003 16:16 > To: Vince DOT Hoffman AT uk DOT circle DOT com > Subject: Re: Using nail on win32 (cygwin) > > > Vince Hoffman wrote: > > > however I also use it on a couple of win32 systems running > under Cygwin (a > > posix compatibility layer for win32) as there is no bsd > mail on cygwin , > > however its tricky to compile on win32 as the name aux is > reserved (just > > creating a text file aux.c is not allowed) so it involves > unpacking it on a > > *nix box and renaming aux.c to something like aux1.c and > doing a quick > > search and replace on references to aux.x and aux.o. > > This is just laughable and another good reason not to use this > 'platform'. > > > Would it be possible to > > change the name of aux.c and aux.o to something more win32 > friendly ? > > No, I generally don't resolve Windows compatibility issues. See > for a good explanation why free > software developers should not do this. > > I'm sorry for the inconvenience this might cause for you as an > individual, but the social issue is more important for me in such > cases and besides, if you have a problem with inconveniences, I'd > advise you not to use Microsoft products at all. > > Gunnar > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/