Print

[kmradke]

Is WIN64 defined (and not just _WIN64) when building APR?

For reference, here is some discussion from the Subversion developers list:
http://svn.haxx.se/dev/archive-2011-02/0816.shtml
http://svn.haxx.se/dev/archive-2011-03/0096.shtml

Not sure if this would only affect the recently released 1.6.16 or not.
http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=260&expandFolder=74

[Gregg]

need both WIN64 & _WIN64 ... seems to be both in APR IIRC ... but _WIN64 should be defined by the compiler .. mine does it I think ... need to check that tho

[mario]

You can find the new version of mod_svn on the download page. Please report any issues.

[kmradke]

You can find the new version of mod_svn on the download page. Please report any issues.

Is this built against the newer openssl libraries included with apache like r2 of 1.6.15?  (The subversion deps usually contains an older version.)

I get an SSL library mismatch error when attempting to run the included executables using the https protocol:

I:\>svn ls https://server/sandbox
svn: OPTIONS of 'https://server/sandbox': SSL handshake failed: SSL disabled due to library version mismatch (https://server)

[kmradke]

Is this built against the newer openssl libraries included with apache like r2 of 1.6.15?  (The subversion deps usually contains an older version.)

I get an SSL library mismatch error when attempting to run the included executables using the https protocol:

I:\>svn ls https://server/sandbox
svn: OPTIONS of 'https://server/sandbox': SSL handshake failed: SSL disabled due to library version mismatch (https://server)

I think this is my problem.  I tried to run the downloaded executables before I copied them to the httpd directory so they were missing ssleay32.dll and libeay32.dll from the apache install.  Once I copied these, I was able to connect via https://.  Sorry about the noise...

[mario]

it is compiled against 1.0.0c

[kmradke]

Is there any way to get notified when you guys release a new 64-bit svn module build (1.6.17 was released recently.)  I hate to just keep asking or repeatedly checking the download page...

[mario]

Sorry for the delay. I'm on it. On the weekend we had some holidays (From Thursday to Sunday.) First build failed. Than I noticed that the tag in svn was not identical to the tarballs.

I give it another shot to morror evening. Thanks for your patience.

[mario]

I have some issues with the zlib component. See the errors from the build log. http://pastebin.com/eDLESGGr (x64 build)
I took zlib-1.2.5, updated sqlite-amalgamation to 3070603, updated neon to 0.29.6

Whole build log http://pastebin.com/byeTyR4R

I have the excat same errors while building the x86 version.

[Gregg]

Looks like it's in need of expat

I hate how VC now can build more than one thing at a time, makes for a nearly impossible read of the log. I set mine to 1 thing at a time, doesn't slow the build down any.

[Gregg]

Looking again I now see the zlib errors, are you sure it is finding what it is in need of, check your /LIBPATH stuff in the link part. Check that it is wanting the right filenames as well. OT example, mod_lua wants lua51.lib where mod_security wants lua5.1.lib .. same file... different filenames.

[Sob]

I'd say that with zlib it's the same problem I had when I tried it for the first time. I did quick test with my non-standard environment (so I can't confirm the whole build process), but for zlib the following seems to do the trick:

Open generated build\win32\build_zlib.bat and insert at line 51 (before "set BUILD_OPTS=..." line):

For x64:

Code: [Select]

set ASM_OPTS=AS=ml64 LOC="-DASMV -DASMINF -I." OBJA="inffasx64.obj gvmat64.obj inffas8664.obj"For x86:

Code: [Select]

set ASM_OPTS=LOC="-DASMV -DASMINF -I." OBJA="inffas32.obj match686.obj"

[mario]

That's wired! I guess I made it like

nmake -f win32/Makefile.msc AS=ml64 LOC="-DASMV -DASMINF -I." OBJA="inffasx64.obj gvmat64.obj inffas8664.obj"

But I'm not fully sure. I gonna try that tonight.


With x86 I'm sure I used
nmake -f win32/Makefile.msc OBJA=inffast.obj

so will have another try. Thanks for the hint!

[mario]

Well my build still fails. But worse 



========== Build: 9 succeeded, 18 failed, 7 up-to-date, 0 skipped ==========


Maybe I start over again with a fresh build.

[mario]

Yes starting over and using zlib from the orig tar ball made the zlib errors go away. 
@Sob Thanks for the hint!!!

There is an issue with neon left. 

http://pastebin.com/8PnM86Tp