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 Date: Fri, 7 Sep 2001 09:18:47 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: atoll(), strtoll(), strtoull() -- where are they? Message-ID: <20010907091847.W537@cygbert.vinschen.de> Mail-Followup-To: cygwin AT cygwin DOT com References: <200109062334 DOT f86NYaJ11685 AT ns1 DOT us DOT xacct 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: <200109062334.f86NYaJ11685@ns1.us.xacct.com>; from Tom.Howland@us.xacct.com on Thu, Sep 06, 2001 at 04:34:41PM -0700 On Thu, Sep 06, 2001 at 04:34:41PM -0700, Tom Howland wrote: > My application uses long long's and unsigned long longs. How do I get these using CYGWIN? As I already wrote in a posting yesterday: - These functions have to go into newlib. There's a newlib mailing list and newlib folks who are willing to accept patches. The official way is to contribute this functions to newlib. Cygwin gets it's standard C lib functions from newlib so these functions will become a part of Cygwin as soon as they are included in newlib and the next Cygwin version will be released. - _DON'T_ take glibc code and offer it to the newlib folks. It will not get into newlib due to licensing constraints. No GPL'd code can make it into newlib for that reason. 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/