Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:57416 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 91574 invoked from network); 18 Jan 2012 19:25:35 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Jan 2012 19:25:35 -0000 Authentication-Results: pb1.pair.com header.from=wrowe@rowe-clan.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=wrowe@rowe-clan.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain rowe-clan.net from 64.202.165.36 cause and error) X-PHP-List-Original-Sender: wrowe@rowe-clan.net X-Host-Fingerprint: 64.202.165.36 smtpauth20.prod.mesa1.secureserver.net Linux 2.4/2.6 Received: from [64.202.165.36] ([64.202.165.36:32868] helo=smtpauth20.prod.mesa1.secureserver.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6B/E2-01828-DAC171F4 for ; Wed, 18 Jan 2012 14:25:34 -0500 Received: (qmail 15411 invoked from network); 18 Jan 2012 19:25:30 -0000 Received: from unknown (76.252.112.72) by smtpauth20.prod.mesa1.secureserver.net (64.202.165.36) with ESMTP; 18 Jan 2012 19:25:30 -0000 Message-ID: <4F171C97.5060208@rowe-clan.net> Date: Wed, 18 Jan 2012 13:25:11 -0600 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: internals@lists.php.net References: <4F16AB37.1070107@lsces.co.uk> <4F16B758.7010206@lsces.co.uk> <4F170372.2080201@rowe-clan.net> <4F170BF7.9010608@lsces.co.uk> In-Reply-To: <4F170BF7.9010608@lsces.co.uk> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] 64bit Windows builds From: wrowe@rowe-clan.net ("William A. Rowe Jr.") On 1/18/2012 12:14 PM, Lester Caine wrote: > 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 SDK and DDK remain free with a minimal toolchain, including 64 bit compilers. Of course they aren't called that anymore, because things are only fun in the Windows world when they overhaul the glossary of terms every 3 years. You probably started with Express edition of Visual Studio, and I note that it claims not to support 64 bit. But the compilers in the SDK or WDK (Windows Drivers Kit formerly DDK) should solve your issue. I don't know offhand whether these contain visual studio 15 or 16.