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, 29 Jun 2000 18:20:26 -0400 To: cygwin@sourceware.cygnus.com Subject: Re: include incompatibilities Message-ID: <20000629182026.B8571@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: cygwin@sourceware.cygnus.com References: <200006292122.XAA02938@mail.arco.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200006292122.XAA02938@mail.arco.de>; from towo@computer.org on Thu, Jun 29, 2000 at 11:22:45PM +0200 On Thu, Jun 29, 2000 at 11:22:45PM +0200, towo@computer.org wrote: >I had lamented about incompatible changes in include files. >May I repeat the practical essence of my previous mail which is the >question: How can these things be detected by #ifdef's without >referring to actual system specifics as below? > >#include >#ifdef __CYGWIN__ /* and version > something ... ! */ >#define sys_nerr _sys_nerr >#define sys_errlist _sys_errlist >#endif > >(On "classical" systems, the exported names are without underlines - >why do these name manglings have to be imposed on us?) I guess "classical" systems does not include linux. You're talking about normal problems with porting software between various systems. This kind of thing is a fact of life that you have to live with. It's the reason for things like autoconf and MetaConfig. Perhaps using one of those two packages is the solution you're straining for. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com