Hi all,
Last week PHP_5_3 out of CVS built on my box under VC6; today it does not.
I have been told on irc (thanks Liz) that there is no intention of fixing
the breakage because 'the 2003 SDK has been a requirement since PHP 5.1'.
This is the first I ever heard of any such requirement - everything has
'just worked' until now with standard out-of-the-box VC6, with or without
SP* applied.
Can someone please either explain the need to break a working build system
just before a PHP release or else revert whatever changes caused the
breakage?
Thanks,
- Steph
hi,
Hi all,
Last week PHP_5_3 out of CVS built on my box under VC6; today it does not.
I have been told on irc (thanks Liz)
It has been like that since literally years. Nothing new under the sun.
that there is no intention of fixing
the breakage because 'the 2003 SDK has been a requirement since PHP 5.1'.
This is the first I ever heard of any such requirement - everything has
'just worked' until now with standard out-of-the-box VC6, with or without
SP* applied.
Service Packs are another story, they have absolutely nothing to do
with the platform SDK. The snaps box does not use the SP6 but will do
it for 5.3+. It does not have impact like binary incompatibilities or
similar bad effects. However the platform SDK 2003/02 is required.
Can someone please either explain the need to break a working build system
just before a PHP release or else revert whatever changes caused the
breakage?
What you may have missed is the minimum windows version. It has been
bumped to 2k/xp a few months ago. What may have happened is the fixes
in TSRM and Zend to do not override this setting. They both use now
the main php setting and it will be settable using configure before
alpha2 (but it will not work for win9x anyway as some APIs were not
available).
The short version is: there is nothing to revert, the snap box works
and you may simply download the right SDK from (I would say, you
should download it if you really want to do the same bins than snaps):
http://www.microsoft.com/msdownload/platformsdk/sdkupdate/psdk-full.htm
Cheers,
Pierre
Hi Pierre,
It has been like that since literally years. Nothing new under the sun.
Erm... no, it hasn't. That's why I'm reporting it now.
that there is no intention of fixing
the breakage because 'the 2003 SDK has been a requirement since PHP 5.1'.
This is the first I ever heard of any such requirement - everything has
'just worked' until now with standard out-of-the-box VC6, with or without
SP* applied.Service Packs are another story, they have absolutely nothing to do
with the platform SDK. The snaps box does not use the SP6 but will do
it for 5.3+.
Sorry, why?
It does not have impact like binary incompatibilities or
similar bad effects. However the platform SDK 2003/02 is required.
Not required until this week. That's exactly what I'm telling you.
Can someone please either explain the need to break a working build
system
just before a PHP release or else revert whatever changes caused the
breakage?What you may have missed is the minimum windows version. It has been
bumped to 2k/xp a few months ago.
Actually we dropped support for Windows 98. I didn't know we'd also dropped
support for NT - if so, there was never any discussion of it on-list.
What may have happened is the fixes
in TSRM and Zend to do not override this setting. They both use now
the main php setting and it will be settable using configure before
alpha2 (but it will not work for win9x anyway as some APIs were not
available).
I don't care about win9x, we agreed to drop support for it at the end of
2006 as I recall. Not quite sure why you're focusing on that here?
The short version is: there is nothing to revert, the snap box works
and you may simply download the right SDK from (I would say, you
should download it if you really want to do the same bins than snaps):http://www.microsoft.com/msdownload/platformsdk/sdkupdate/psdk-full.htm
It wants far more space than I actually have on my laptop hard drive. I
can't quite believe you're actually making this a requirement for the
first time just before a release.
- Steph
http://www.microsoft.com/msdownload/platformsdk/sdkupdate/psdk-full.htm
It wants far more space than I actually have on my laptop hard drive. I
can't quite believe you're actually making this a requirement for the
first time just before a release.
Uninstall the old one, install the new one, et voila, no need to kill
a cat to get that solved. Now that we have cleared the true issue, let
us go back to work :)
Cheers,
Uninstall the old one, install the new one, et voila, no need to kill
a cat to get that solved. Now that we have cleared the true issue, let
us go back to work :)
Hard drive has 2.02 gigs, SDK installment requires 'at least 1.4 GB'. No
way, can't risk it, I need this laptop for work.
The true issue is that the build worked here until a few days ago, without
the need to upgrade or install anything, and no longer does. You want to
move the Windows stuff on from VC6, fine, but you actually just dropped
support for it during the final moments of a release cycle and that is not
fine. You're also being more than a little ingenuous in declaring that
there's been no change in the requirements. The crypt changes included a
specific change in the requirements, and since you wrote it, you cannot
possibly be unaware of that fact.
It might have been wise to advertise that change in requirements before
committing the patch - or to find some way around it.
- Steph
Hi all,
Last week PHP_5_3 out of CVS built on my box under VC6; today it does not.
I have been told on irc (thanks Liz)
It has been like that since literally years. Nothing new under the sun.
Uh, last time I tried it worked fine with MSVC6. So this is definitely
something new.
regards,
Derick
--
HEAD before 5_3!: http://tinyurl.com/6d2esb
http://derickrethans.nl | http://ezcomponents.org | http://xdebug.org
Hi all,
Last week PHP_5_3 out of CVS built on my box under VC6; today it does not.
I have been told on irc (thanks Liz)
It has been like that since literally years. Nothing new under the sun.
Uh, last time I tried it worked fine with MSVC6. So this is definitely
something new.
What Steph is talking about is the Platform SDK and maybe the Service Pack.
Visual C++ 6 worked and will always work for 5.3.
Cheers.
Pierre
What Steph is talking about is the Platform SDK and maybe the Service
Pack.
? Having now discovered ('course the wretched thing won't tell me so I have
to compare file versions) that I did in fact have SP 6 applied, the problem
is that you now need the Platform SDK too.
Visual C++ 6 worked and will always work for 5.3.
So long as you... etc etc etc. I still think if there's a way around this we
should find it, I'll do some digging.
- Steph
Derick Rethans wrote:
Hi all,
Last week PHP_5_3 out of CVS built on my box under VC6; today it does not.
I have been told on irc (thanks Liz)
It has been like that since literally years. Nothing new under the sun.
Uh, last time I tried it worked fine with MSVC6. So this is definitely
something new.regards,
Derick
It builds fine with VC 6. Is it too much to ask that people use an
updated SDK (note that updated still is over 5 years old)?
Rob
It builds fine with VC 6. Is it too much to ask that people use an
updated SDK (note that updated still is over 5 years old)?
That's not the issue... The issue is more that nobody asked it until now.
- Steph