Hi Stefan,
Sorry to say this still will not build and just changes the error message.
I however would like to see 2.3.6 out this week as well as everyone
else. If worse comes to worse, #ifndef WIN32 around this one line
does allow apache to compile and run, and a quick testing it seems to
not be causing problems with normal logging. It may not have the desired
new functionality you are looking for but as AFAIK this is still going
to be under the alpha banner, so, no big deal.
That said, I still have to wrap my head around the docs of the new
functionality which I plan to do after the release. I can then see if it
does, does not or partially does work should I succeed in understand
the new fuctionality. This would also takes some pressure off Bill to
scramble up his patch as he mentioned. Simply note in the source above
the workaround that it may not be correct but is a temporary workaround
to allow the server to be compiled on Windows. Of course, this is your
guy's call.
Regards,
Gregg
Stefan Fritsch wrote:
Hi Gregg,
On Monday 07 June 2010, Gregg L. Smith wrote:
This seems to break trunk on Windows, prior revision builds fine.
I am not really familiar with the difference between AP_DECLARE_DATA
and AP_MODULE_DECLARE_DATA or any other Windows build pecularities.
Maybe the attached patch helps?
Cheers,
Stefan
William A. Rowe Jr. wrote:
On 6/7/2010 1:41 AM, Gregg L. Smith wrote:
Hi Stefan,
This seems to break trunk on Windows, prior revision builds fine.
--------------------Configuration: httpd - Win32
Release--------------------
Compiling resources...
Compiling...
main.c
E:\build\httpd-2.3.x-wrk\server\main.c(48) : warning C4273:
'core_module' : inconsistent dll linkage. dllexport assumed.
Linking...
main.obj : error LNK2001: unresolved external symbol _core_module
Release/httpd.exe : fatal error LNK1120: 1 unresolved externals
I'll work up a patch when I finish my workday.
