Hi Steffen,

Am 10.04.2018 um 12:36 schrieb Steffen:

Fits the subject:  someone says he has  success , but I have no success to build Trunk revision 1828799 (current).

OK, I got confused by your followup mail talking about copying files from trunk to 2.4.

By the way: this "someone" is buildbot, an automated system making a standardized (unix) build for trunk and sending a mail, whenever the build status changes. We tyicaly reply to these mails, if the buildbot build fails and we want to discuss why it failed.

For problems observed during our own testing we typically start a new descriptive mail thread.

Error C2440 'function': cannot convert from 'int (__stdcall *)(conn_rec *)' to 'ap_HOOK_output_pending_t (__cdecl *)'libhttpd...\trunk\server\core.c5724

Had to remove an unused hook  in core.c :

     ap_hook_output_pending(ap_filter_output_pending, NULL, NULL,
             APR_HOOK_MIDDLE);

Now I am confused again. These are new errors? Or is it your first attempt of building trunk? The code was introduced back in 2016:

------------------------------------------------------------------------
r1734656 | minfrin | 2016-03-12 01:43:58 +0100 (Sat, 12 Mar 2016) | 3 lines

core: Extend support for setting aside data from the network input filter
to any connection or request input filter.

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

I don't think the code is unused, so it should not be removed. Unfortunately I don't know enough about how hooks work on Windows to propose a solution.

Builds fine now with OpenSSL 1.1.1 pre4, tls1.3 test looks promising.

Thanks.

The below errors was my fault, was mixing, sorry.

OK, no problem.

Regards,

Rainer

On Monday 09/04/2018 at 19:22, Rainer Jung wrote:
Hi Steffen,

are the below errors you reported from building trunk or from building 2.4? Your mail subject was "Re: buildbot success in on httpd-trunk" so I thought trunk but after trying for quite some time couldn't find any reason for problems there. Your second email makes me wonder whether you copied trunk files to a 2.4 source tree, which is in most cases not a good idea.

So can you clarify what you tried and choose an appropriate email subject, so tat we can see from the subject, what the topic is?

Thanks and regards,

Rainer

Am 09.04.2018 um 16:59 schrieb Steffen:
Looks cannot build without other sources from trunk, like maybe ap_mmn.h util_filter.h core_filters.c request.c util_filter.c
Can we have a patch for 2.4 ?
On Monday 09/04/2018 at 16:37, Steffen wrote:
Current trunk still does  not build mod_ssl on windows:

Got:
ssl_engine_io.obj : error LNK2019: unresolved external symbol _ap_filter_reinstate_brigade referenced in function _ssl_io_filter_output ssl_engine_io.obj : error LNK2019: unresolved external symbol _ap_filter_should_yield referenced in function _ssl_io_filter_output ssl_engine_io.obj : error LNK2019: unresolved external symbol _ap_filter_setaside_brigade referenced in function _ssl_io_filter_output

And warnings with same vcar's:
WarningC4013'ap_filter_reinstate_brigade' undefined; assuming extern returning intmod_sslc:\vc15\win32\httpd-2.4\modules\ssl\ssl_engine_io.c1782 WarningC4013'ap_filter_should_yield' undefined; assuming extern returning intmod_sslc:\vc15\win32\httpd-2.4\modules\ssl\ssl_engine_io.c1808 WarningC4013'ap_filter_setaside_brigade' undefined; assuming extern returning intmod_sslc:\vc15\win32\httpd-2.4\modules\ssl\ssl_engine_io.c1865


Cannot figure out if I miss an include.


On Monday 09/04/2018 at 16:17, build...@apache.org wrote:

      The Buildbot has detected a restored build on builder httpd-trunk
      while building . Full details are available at:
https://ci.apache.org/builders/httpd-trunk/builds/1995

      Buildbot URL: https://ci.apache.org/

      Buildslave for this Build: bb_slave6_ubuntu

      Build Reason: The AnyBranchScheduler scheduler named
      'httpd-trunk-on-commit' triggered this build
      Build Source Stamp: [branch httpd/httpd/trunk] 1828723
      Blamelist: icing

      Build succeeded!

      Sincerely,
      -The Buildbot

Reply via email to