Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Fri, 10 Aug 2001 09:01:29 +0200
From: Corinna Vinschen <cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: xinetd...
Message-ID: <20010810090129.W530@cygbert.vinschen.de>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20010810025014 DOT 57544 DOT qmail AT web20006 DOT mail DOT yahoo DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20010810025014.57544.qmail@web20006.mail.yahoo.com>; from tdorgan@yahoo.com on Thu, Aug 09, 2001 at 07:50:14PM -0700

On Thu, Aug 09, 2001 at 07:50:14PM -0700, Tom Dorgan wrote:
> ok, so I got the sources for xinetd-2.3.0 from www.xinetd.org. ran into
> some issues on the build (very standard -./configure, make, make
> install). however, uint64_t, is undefined. I trace this to stdint.h and
> a short thread from last year which indicates that it is not available.
> 
> however, on cygwin, the file /usr/include/mingw/stdint.h does exist. my
> question is, do I use this or what? If I do, Im not sure where to add
> an extra include path for the cygwin platform. I certainly dont want to
> hack up the xinetd release package so Im asking for advice here.

But that's the whole thing when porting. You hack the release stuff so
that it contains OS specific changes for the new OS (here Cygwin) in
the least intrusive way possible. When finished, you contact the
maintainer of the package if s/he's willing to add the new OS specific
changes to the main trunk like it's mostly already done for Linux, BSD,
Solaris,... before.

Adding an include path is probably best to add to configure.in.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
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/