Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Thu, 25 May 2000 12:05:53 -0400 To: cygwin@sourceware.cygnus.com Subject: Re: CygUtils Version of zip (and Symlinks) Message-ID: <20000525120553.E1330@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: cygwin@sourceware.cygnus.com References: <200005251558.IAA25370@cygnus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200005251558.IAA25370@cygnus.com>; from rdparker@butlermfg.com on Thu, May 25, 2000 at 10:56:53AM -0500 On Thu, May 25, 2000 at 10:56:53AM -0500, Parker, Ron wrote: >This may be more a question for cygwin-developers, but I hate crossposts and >know most readers of that list at least review this one. So, wouldn't it be >appropriate when compiling without -mno-cygwin for the specs file to define >"unix", "UNIX" and similar "standard" defines? They seem to be checked for >in newlib, zlib, X11, and many other sources? I don't see why it would be appropriate to define UNIX when you're specifying a command line option that says "This is not UNIX". So, no, I don't believe that this is appropriate. I don't even know that newlib will build correctly with -mno-cygwin. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com