RE: [PECL-DEV] building php_inclued_dll / unresolved external symbol _executor_globals

[email protected] ("Neuhauser, Roman (GE Capital, consultant)")
Newsgroups php.pecl.dev
Message-ID <D3A73269432A224FA3E7ECE3DDDFCE40045ED7C9@LONMLVEM10.e2k.ad.ge.com>
From: Pierre Joye [mailto:[email protected]] 
> On Wed, Aug 11, 2010 at 12:40 PM, Neuhauser, Roman (GE Capital,
> consultant) <[email protected]> wrote:
> > i'm trying to build php_inclued.dll.  i've concocted a config.w32
> > file (see below) which allows the extension to build statically,
> > but the dll build bombs:
> >
> > inclued.obj : error LNK2019: unresolved external symbol _executor_globals referenced in function _pack_output
> > inclued_zend.obj : error LNK2001: unresolved external symbol _executor_globals
> > inclued.obj : error LNK2019: unresolved external symbol _zval_used_for_init referenced in function _zm_activate_inclued
> > inclued_zend.obj : error LNK2019: unresolved external symbol _php_plain_files_wrapper referenced in function _add_include
> > Release\php_inclued.dll : fatal error LNK1120: 3 unresolved externals
> > NMAKE : fatal error U1077: '"c:\Program Files\Microsoft Visual Studio 9.0\VC\Bin\cl.exe"' : return code '0x2'
> > Stop.
> 
> Sounds like a nmake clean is required here first, certainly buildconf
> & configure too if you changed the config.w32.

i know that and did that.

> >  configure --disable-all --disable-zts --enable-cli 
> --enable-inclued=shared
> 
> Now I'm confused, do you want it static or shared?

what about the configure command line confuses you? i thought i was quite clear:

> > i'm trying to build php_inclued.dll.  i've concocted a config.w32
> > file (see below) which allows the extension to build statically,
> > but the dll build bombs

anyways, the issue is already resolved, 0.1.1 doesn't build the shared lib, trunk does.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.