Edin Kadribasic wrote: > Hi Andi, > > Turns out the problem is that Apache is building their binaries using > VC6 so wrong CRT gets loaded. The only solution I found was to tell > Windows to load Apache with msvcr80.dll instead of msvcr.dll by suppling > a manifest file in Apache bin directory. If you crate > Apache.exe.manifest that contains: > > <?xml version='1.0' encoding='UTF-8' standalone='yes'?> > <assembly xmlns='urn:schemas-microsoft-com:asm.v1' manifestVersion='1.0'> > <dependency> > <dependentAssembly> > <assemblyIdentity type='win32' name='Microsoft.VC80.CRT' > version='8.0.50608.0' processorArchitecture='x86' > publicKeyToken='1fc8b3b9a1e18e3b' /> > </dependentAssembly> > </dependency> > </assembly> > > The Apache will load PHP and PHP will be able to load extensions. It > probably isn't good idea to force a different C Runtime on Apache like this.
FYI - If Apache adopted this convention, it would break on systems without the VC80 CRT - but worse... VC80 carries the baggage of installing WinSXS (side by side assemblies) for anything pre-XP. There are Apache VC80 binaries generated by others. But because Apache means to interoperate (for today) with ActivePerl/ActivePython, we weren't prepared to mess around any further with the breadth of bogosity that VC8 introduces. Apache's actively picking it up for source code builders, as I suggested in an earlier posting. From the ASF's perspective - folks exploring the Source is always the primary mission of the foundation. Will Apache bump to VC 7.1 or 8.0 with Apache 2.4? Who knows. But Apache 2.0 (as distributed) is legacy - it will never veer into VC7+ territory. And Apache 2.2 already shipped with VC6, so it's unlikely to change, as well. Mitigate binary compatibility breakage is the buzzword once an even-minor version has shipped. (Odd-minor's e.g. 2.3 are a moving target/development branch - no hassle there of disrupting users). A last interesting question; what sort of headaches have you hit loading within the ISAPI/IIS environment? I would presume that older/modern IIS flavors suffer from similar headaches? I do hang around here, so will be very curious to keep on top of the PHP project's progress w.r.t. Studio 2005. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
