Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:57415 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 86834 invoked from network); 18 Jan 2012 18:14:22 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Jan 2012 18:14:22 -0000 Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.20.125 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 213.123.20.125 c2bthomr07.btconnect.com Received: from [213.123.20.125] ([213.123.20.125:45504] helo=mail.btconnect.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 74/42-01828-BFB071F4 for ; Wed, 18 Jan 2012 13:14:20 -0500 Received: from host81-138-11-136.in-addr.btopenworld.com (EHLO _10.0.0.4_) ([81.138.11.136]) by c2bthomr07.btconnect.com with ESMTP id GAV26452; Wed, 18 Jan 2012 18:14:16 +0000 (GMT) Message-ID: <4F170BF7.9010608@lsces.co.uk> Date: Wed, 18 Jan 2012 18:14:15 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20111220 Firefox/9.0.1 SeaMonkey/2.6.1 MIME-Version: 1.0 To: PHP internals References: <4F16AB37.1070107@lsces.co.uk> <4F16B758.7010206@lsces.co.uk> <4F170372.2080201@rowe-clan.net> In-Reply-To: <4F170372.2080201@rowe-clan.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Mirapoint-IP-Reputation: reputation=Good-1, source=Queried, refid=tid=0001.0A0B0303.4F170BF7.0085, actions=TAG X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2012.1.18.173314:17:7.586, ip=81.138.11.136, rules=__MOZILLA_MSGID, __HAS_MSGID, __SANE_MSGID, __USER_AGENT, __MIME_VERSION, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __CT, __CT_TEXT_PLAIN, __CTE, __ANY_URI, __URI_NO_MAILTO, __CP_URI_IN_BODY, __OEM_SOFTWARE_1, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_2000_2999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, RDNS_SUSP, OEM_SOFTWARE_X1, BODY_SIZE_7000_LESS X-Junkmail-Status: score=10/50, host=c2bthomr07.btconnect.com X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0202.4F170BF8.0013:SCFSTAT14830815,ss=1,re=-4.000,fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=multiengine X-Junkmail-IWF: false Subject: Re: [PHP-DEV] 64bit Windows builds From: lester@lsces.co.uk (Lester Caine) William A. Rowe Jr. wrote: > On 1/18/2012 6:13 AM, Lester Caine wrote: >> > >> > A much better reason for not supporting the build is probably that the 64bit compiler is >> > not available in the free development stack? We have to buy a development stack to get the >> > 64bit compiler which blocks rather than working with the publicly available process:( >> > But actually that is a better reason for supplying a 64 bit build, and why others are >> > providing that service. > Actually, no. There are any number of free mechanisms to build 64 bit code. Could you elaborate on that? Building 64bit windows applications which are VC9 compliant would seem to need the 'official' compiler, and while I have not done a lot of looking, there was nothing being offered when I tried to set up the windows build environment form Pierre's original notes although that was some time ago. I ended up buying an M$ development pack to plug the hole. > The root problem is that Windows "WIN64" is a 64P architecture. Linux and > *nix variants, on the other hand, are 64ILP or 64LP. Meaning Windows has > longs/ints which are undersized compared to the *nix brethren. The old and > stale abuse such as unsigned long X = (unsigned long)pY; will not do what > the author intended. > > This means all packages ported to *nix 64 bits may have very serious flaws > which have not been fixed for*Windows 64 bit* architecture. I'd anticipate > CoApp identifying and resolving most of these applicable to PHP over the > coming months, but it is a non-trivial problem requiring a number of pairs > of eyeballs to get right. I do accept that there are inherent problems with the current unsupported builds, my own sites have not had any errors in serving PHP pages via a 64bit Apache/PHP/Firebird stack on 64 bit windows XP. But I am more than happy to help if a serious effort is made to tidy this up, and I still have two sites that I can soak test on, although one of them is scheduled to switch to Linux in the next six months. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk// Firebird - http://www.firebirdsql.org/index.php