Bug #70530 [Fbk->Csd]: php_uname function output wrong information

From: Date: Fri, 25 Sep 2015 13:38:15 +0000
Subject: Bug #70530 [Fbk->Csd]: php_uname function output wrong information
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-196239@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=70530&edit=1

 ID:                 70530
 User updated by:    khaweronline at gmail dot com
 Reported by:        khaweronline at gmail dot com
 Summary:            php_uname function output wrong information
-Status:             Feedback
+Status:             Closed
 Type:               Bug
 Package:            PHP options/info functions
 Operating System:   Win 10 32 Bit
 PHP Version:        5.6.11
 Block user comment: N
 Private report:     N

 New Comment:

Thanks for your comments PHP Team. After reading your comments, i downloaded PHP 5.6.12 and replaced
my XAMPP Pre installed PHP with the downloaded one.
But still it showed me Windows 8 Professional Edition instead of Windows 10 Professional Edition. So
far i don't known whether this is Bug in PHP or XAMPP. That's why i m closing this BUG.
If anyone report same issue in PHP, please reopen this bug.


Previous Comments:
------------------------------------------------------------------------
[2015-09-22 13:16:48] ab@php.net

Yeah, XAMPP is the keyword. I guess I understand what happens.

Every PHP binary now integrates the manifest which makes all the version functionality work under
win10. However, for that to work, the binaries that load PHP have to have integrated manifests, too.
So say in this case, if loading the PHP module into Apache, httpd.exe has to have an embedded
manifest.

PHP itself, say CLI, integrates manifests (actually everywhere into DLLs and executables).
@khaweronline if you try CLI, it should show correct results. But we're not in control of the
XAMPP builds, so probably those have no embedded manifests. The ones I know doing that are from
apachelounge.com, one can try them.

To embed a manifest, it is not necessary to recompile the binary. If you have Visual Studio
installed, you can do it with your XAMPP bins https://msdn.microsoft.com/en-us/library/vstudio/ms235591%28v=vs.100%29.aspx
. But anyway, how it looks like, it's something to be reported to the XAMPP project.
@khaweronline, maybe you could do it also linking to the ticket mentioned by @requinix.

Thanks.

------------------------------------------------------------------------
[2015-09-21 19:06:36] requinix@php.net

XAMPP? Don't they build their own PHP?

------------------------------------------------------------------------
[2015-09-21 18:51:24] khaweronline at gmail dot com

Please check these screenshots this may help

http://s4.postimg.org/56qohkwwd/sc1.jpg
http://s21.postimg.org/4qmzrr5ef/sc2.jpg

------------------------------------------------------------------------
[2015-09-21 11:39:34] ab@php.net

I've just tried, specifically downloaded 5.6.11 and what i see on my box is

> php -n -r "echo php_uname();"
Windows NT PHP-DEV 10.0 build 10240 (Windows 10) AMD64

So not sure what could be strange. Build 9200 is indeed from some Win 8 and Server 2012 series. It
was also used in some early technical previews, which made it to be recognized as win8. Any chance
you use some technical preview still? And, do you use the official PHP binaries?

Thanks.

------------------------------------------------------------------------
[2015-09-20 09:18:46] khaweronline at gmail dot com

I am using Windows 10 Pro 32 bit and PHP 5.6.11

------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    https://bugs.php.net/bug.php?id=70530


--
Edit this bug report at https://bugs.php.net/bug.php?id=70530&edit=1


Thread (9 messages)

« previous php.bugs (#196239) next »