osdir.com

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [users@httpd] facing issue with building apache for latest version 2.4.33


Hello,

Am 06.04.2018 um 08:41 schrieb Rathore, Rajendra:
Hi Team,

I am facing the issue while building apache on Window machine with the help of apache source code and got below error

[ 92%] Building C object CMakeFiles/mod_ssl.dir/modules/ssl/ssl_engine_init.c.obj

ssl_engine_init.c

C:\apacheBuild\apache2.4\build\httpd-2.4.33\modules\ssl\ssl_engine_init.c(33) : fatal error C1083: Cannot open include file: 'mod_md.h': No such file or directory

NMAKE : fatal error U1077: 'c:\PROGRA~2\MICROS~2.0\VC\bin\amd64\cl.exe' : return code '0x2'

Stop.

I did some investigation and found that with new version of apache we added a new module called *mod_md* which is experimental basis, I don’t know why experimental module added as a dependency and it will cause a build failure,

Can you please help me out to fix above issue?

for people who are not aware: the OP opened th eissue https://bz.apache.org/bugzilla/show_bug.cgi?id=62266 and I commented there, that this seems to be a cmake specific problem and proposed to test the following fix:

Index: CMakeLists.txt
===================================================================
--- CMakeLists.txt      (revision 1828523)
+++ CMakeLists.txt      (working copy)
@@ -649,6 +649,7 @@
   ${CMAKE_CURRENT_SOURCE_DIR}/modules/dav/main
   ${CMAKE_CURRENT_SOURCE_DIR}/modules/filters
   ${CMAKE_CURRENT_SOURCE_DIR}/modules/generators
+  ${CMAKE_CURRENT_SOURCE_DIR}/modules/md
   ${CMAKE_CURRENT_SOURCE_DIR}/modules/proxy
   ${CMAKE_CURRENT_SOURCE_DIR}/modules/session
   ${CMAKE_CURRENT_SOURCE_DIR}/modules/ssl

This should fix building mod_ssl, ie. the OP's original question.

To build mod_md itself is not yet supported by our cmake files.

Regards,

Rainer


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx