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 Date: Fri, 30 Aug 2002 07:41:47 +0200 From: "Gerrit P. Haase" Organization: Esse keine toten Tiere X-Priority: 3 (Normal) Message-ID: <4297036465.20020830074147@familiehaase.de> To: mike CC: cygwin AT cygwin DOT com Subject: Re: BUILDING PHP4.2.2 on Windows using supplied .DSW, MS VS C++ 6.0, and Cygwin Headers? In-Reply-To: <1030683319.3d6efab7e8ff7@peer2peerporn.com> References: <1030683319 DOT 3d6efab7e8ff7 AT peer2peerporn DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hallo mike, Am Freitag, 30. August 2002 um 06:55 schriebst du: > Hi, I've been trying to compile PHP on Windows for days. [...] > I see that in cygwin sys/types.h uses "long long" to define a 64 bit value, but > Microsoft calls them "__int64". I can change the cygwin typedefs from long long > to __int64, but it's hard to think that this would be required without someone > describing this somewhere... [...] > Is this a PHP problem, a Cygwin problem, a Visual Studio problem, or a Me > problem? Can you use Cygwin headers with MS VC++ 6.0? Hmmm, I would say a MS problem. They don't follow the standards. long long is pretty standard, they allow longlong (IIRC) or call it different (__int64). Gerrit -- =^..^= -- 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/