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

 ID:                 61175
 Comment by:         mattfic...@php.net
 Reported by:        jmc at chakra-project dot org
 Summary:            The sapi/embed/php_embed.h header is not included in
                     a custom Win32 snapshot
 Status:             Open
 Type:               Bug
 Package:            Unknown/Other Function
 Operating System:   Windows XP Professional SP3
 PHP Version:        5.3.10
 Block user comment: N
 Private report:     N

 New Comment:

I can reproduce this problem too.

It sounds like this is a low priority issue, sorry.

If you have a fix for this problem, could you post it here, so it'll get 
committed at some point.


Thank you for helping to make PHP better.


Previous Comments:
------------------------------------------------------------------------
[2012-02-24 10:57:32] jmc at chakra-project dot org

Description:
------------
I've fetched a fresh SVN snapshot from the 5.3.10 branch 
(https://svn.php.net/repository/php/php-src/branches/PHP_5_3_10), and 
configured 
it as follows:

configure --with-prefix=<INSTALL_DIR>
          --enable-cli
          --enable-embed=static
          --enable-zend-multibyte
          --enable-mbstring
          --enable-intl
          --disable-cgi

I then compiled PHP and made a custom snapshot archive for internal usage with 
"nmake snap", but it seems like the sapi/embed/php_embed.h header was not 
copied 
to the Release_TS directory.

I can replicate this behavior on both a Windows XP Professional SP3 machine and 
a Windows 7 Professional machine. My compiler is MSVC2008 (from Visual C++ 2008 
Express), and the Microsoft Windows SDK v6.1 is installed.

Expected result:
----------------
The sapi/embed/php_embed.h header should be included with the snapshot.

Actual result:
--------------
The sapi/embed/php_embed.h header is left out of the snapshot.


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



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

Reply via email to