php-windows Digest 11 May 2009 10:57:56 -0000 Issue 3620
Topics (messages 29323 through 29325):
Re: [PHP-DEV] Non blocking file i/o support for win32.
29323 by: Kalle Sommer Nielsen
Win32 snapshot builds.
29324 by: Richard Quadling
snmpapp.conf is broken and php cant work
29325 by: Andrey Wolk
Administrivia:
To subscribe to the digest, e-mail:
[email protected]
To unsubscribe from the digest, e-mail:
[email protected]
To post to the list, e-mail:
[email protected]
----------------------------------------------------------------------
--- Begin Message ---
Hi Richard
2009/5/8 Richard Quadling <[email protected]>:
> Hi.
>
> Can anyone with windows knowledge take a quick look at
> http://bugs.php.net/bug.php?id=47918. I'm pretty sure this IS a bug.
> I'm hoping you don't say it is a documentation bug and it is something
> you can fix.
>
> My requirement is to allow non-blocking file i/o.
>
> With non-win32, it seems that the fcntl() function can accept
> O_NONBLOCK. This does not seem to be present on win32.
fcntl() is not available on Windows aswell as O_NONBLOCK, but after
some small research we could perhaps use the iocsocket() function with
the FIONBIO flag to emulate O_NONBLOCK on Windows.
>
>
> The doc for fopen() does not mention 'n' as being available (probably
> for this reason).
The 'n' mode was added in 5.3 RC2 by Mikko, but has not yet been documented.
>
>
> Regards,
>
> Richard.
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
--
Kalle Sommer Nielsen
[email protected]
--- End Message ---
--- Begin Message ---
Hi.
The x86 Win32 snapshots haven't been built since 2009-May-07 20:00:00
(according to cache.info). (Can see no errors).
The x86 build is building a PECL package (xdebug (vc6/9) and apc (vc6)).
The x64 Win32 snapshots have a build issue also. The tail end of
http://windows.php.net/downloads/snaps/compile-5.3-VC9-x64-latest.log
shows ...
Copying php_xmlrpc.dll from x64\Release_TS to
x64\Release_TS/php-5.3.0RC3-dev/ext
Copying php_xsl.dll from x64\Release_TS to x64\Release_TS/php-5.3.0RC3-dev/ext
WARNING: distro depends on msvcr90.dll, but could not find it on your system
WARNING: you don't have a snapshot template
your dist will not be complete
cd x64\Release_TS\php-5.3.0RC3-dev
zip.exe -9 -q -r ..\php-5.3.0RC3-dev-Win32-VC9-x64.zip .
cd ..\..
cd x64\Release_TS\pecl-5.3.0RC3-dev
NMAKE : fatal error U1077: 'cd' : return code '0x1'
Stop.
It seems that the main difference here is the presence of the "x64"
folder and the ..\.. does not take into account the extra level.
The tail of
http://windows.php.net/downloads/snaps/compile-5.3-VC9-x86-latest.log
shows ...
Copying php_apc.dll from Release_TS to Release_TS/pecl-5.3.0RC3-dev
Copying php_xdebug.dll from Release_TS to Release_TS/pecl-5.3.0RC3-dev
WARNING: distro depends on msvcr90.dll, but could not find it on your system
WARNING: you don't have a snapshot template
your dist will not be complete
cd Release_TS\php-5.3.0RC3-dev
zip.exe -9 -q -r ..\php-5.3.0RC3-dev-Win32-VC9-x86.zip .
cd ..\..
cd Release_TS\pecl-5.3.0RC3-dev
zip.exe -9 -q -r ..\pecl-5.3.0RC3-dev-Win32-VC9-x86.zip .
cd ..\..
cd Release_TS\php-test-pack-5.3.0RC3-dev
zip.exe -9 -q -r ..\php-test-pack-5.3.0RC3-dev.zip .
cd ..\..
cd Release_TS
zip.exe -9 -q php-debug-pack-5.3.0RC3-dev-Win32-VC9-x86.zip *.pdb
cd ..\..
No, "x64" folder.
The zips are created but not pecl package.
Regards,
Richard
--
-----
Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
"Standing on the shoulders of some very clever giants!"
--- End Message ---
--- Begin Message ---
My PHP works under IIS as ISAPI extention.
A few scripts are run under php-cgi.exe
php_snmp.dll is set in php.ini
Sometimes, when a script calls snmp function,
c:\usr\SNMP\PERSIST\snmpapp.conf breaks. After that IIS cannot run
scripts. php-cgi.exe warn me simething like "cannot load module" and
cannot run scripts too. All I can do is deleting snmpapp.conf. Next time
PHP forks fine until new problem with this file.
http://bugs.php.net/bug.php?id=48213
--- End Message ---
