On Tue, Dec 1, 2015 at 7:15 AM, Jan Ehrhardt <php...@ehrhardt.nl> wrote:
> Jim Jagielski in gmane.comp.apache.devel (Tue, 1 Dec 2015 07:38:47 -0500): > > > >> On Nov 30, 2015, at 5:53 PM, Jan Ehrhardt <php...@ehrhardt.nl> wrote: > >> > >> Creating library .\Release/mod_http2.lib and object > .\Release/mod_http2.exp > >> 1>h2_from_h1.obj : error LNK2019: unresolved external symbol > _ap_casecmpstr > >> referenced in function _create_response > >> 1>.\Release\mod_http2.so : fatal error LNK1120: 1 unresolved externals > > > >Sounds like you needed to do a make clean and rebuild... ap_casecmpstr() > >is httpd not APR :) > > If only it was that simple on Windows. Replacing all sources of 2.4.x with > those from trunk leads to oher errors. Hi Jan - it isn't possible to build httpd trunk sources using httpd 2.4.x build files, and this goes for windows or unix. How were you trying to build? ... > For instance: > > 1>------ Build started: Project: mod_ssl, Configuration: Release Win32 > ------ > 1> mod_ssl.c > 1>mod_ssl.c(43): error C2491: 'ssl_run_pre_handshake': definition of > dllimport > function not allowed > 1> ssl_engine_config.c > 1> ssl_engine_init.c > 1>ssl_engine_init.c(39): error C2491: 'ssl_run_init_server': definition of > dllimport function not allowed > etc > Right now, SSL_DECLARE_EXPORT is defined in both mod_ssl.dsp, from the ancient build schema, and in CMakeFiles.txt, for our new and still evolving cmake-based build schema. It seems like you may have been trying to build mod_ssl in trunk using the mod_ssl.mak file from 2.4.x? Someone can generate you the .mak files for trunk, we just don't check them in during trunk development because they are a more rapidly moving target that doesn't settle down till we are about ready to release trunk as some 2.6 or 3.0 version. That's what the cmake effort is all about. See the README.cmake in the root httpd trunk directory for guidance on how to use that. If that is what you did, then we have a bigger issue to resolve, but I compared the use of SSL_DECLARE_EXPORT to the long-existing DAV_DECLARE_EXPORT and it seems to be consistent. Cheers, Bill
