Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
From: "Cooke, Mark" <mark.cooke@siemens.com>
To: "users@subversion.apache.org" <users@subversion.apache.org>
CC: Stefan Hett <stefan@egosoft.com>,
        Pavel Lyalyakin
	<pavel.lyalyakin@visualsvn.com>
Subject: RE: Compiling svn + httpd for windows python 2.x
Thread-Topic: Compiling svn + httpd for windows python 2.x
Thread-Index: AdHMcQBH1yFfMnsjS72EYCotRtNpy///8YkA///duXCAAC9iAP//r0nQgACNqID//8v60A==
Date: Wed, 22 Jun 2016 17:13:30 +0000
Message-ID: <AFFC460063A40F4BB5A536CE937EA754376F79@DEFTHW99EL4MSX.ww902.siemens.net>
References: <AFFC460063A40F4BB5A536CE937EA754376D8B@DEFTHW99EL4MSX.ww902.siemens.net>
 <b5bc3b98-2469-28da-d148-a64f7ecdd05f@egosoft.com>
 <AFFC460063A40F4BB5A536CE937EA754376DB5@DEFTHW99EL4MSX.ww902.siemens.net>
 <cf637e03-a991-26c4-8ca9-f139eec468be@egosoft.com>
 <AFFC460063A40F4BB5A536CE937EA754376F2E@DEFTHW99EL4MSX.ww902.siemens.net>
 <f8c724a5-f676-936b-a3de-e73d8f0fe5fd@egosoft.com>
In-Reply-To: <f8c724a5-f676-936b-a3de-e73d8f0fe5fd@egosoft.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
archived-at: Wed, 22 Jun 2016 17:13:47 -0000

> -----Original Message-----
> From: Stefan Hett [mailto:stefan@egosoft.com]
> Sent: 22 June 2016 17:03
>=20
> On 6/22/2016 5:30 PM, Cooke, Mark wrote:
> >
> >> -----Original Message-----
> >> From: Stefan Hett [mailto:stefan@egosoft.com]
> >> Sent: 22 June 2016 13:25
> >>
> >> On 6/22/2016 2:01 PM, Cooke, Mark wrote:
> >>>> -----Original Message-----
> >>>> From: Stefan Hett [mailto:stefan@egosoft.com]
> >>>> Sent: 22 June 2016 12:38
> >>>>
> >>>> Hi Mark,
> >>>>
> >>>>> Folks,
> >>>>>
> >>>>> We use subversion with Trac behind httpd on Windows Server.  As Tra=
c
> >>>>> is written in "old" Python (2.x), I have had to resort to building
> >>>>> everything from source.  This is not simple and so I thought I woul=
d
> >>>>> publish my notes here in case it helps anyone else and in the hope
> >>>>> that if I have made any mistakes, someone will be kind enough to
> >>>>> point them out to me!
> >>>>>
> >>>>> ~ Mark C
> >>>>>
> >>>>> These are my notes for building Apache httpd and subversion for use
> >>>>> with Trac [1].  All of the components need to be built using the sa=
me
> >>>>> compiler to avoid run-time issues and, since Trac currently relies =
on
> >>>>> Python 2.x, that means Visual Studio 2008.
> >>>> Why does Python 2.x (aka: 2.7.11) imply having to use VS 2008? MaxSV=
N
> >>>> [1] is built using VS 2015 Update 1 (the upcoming builds will use VS
> >>>> 2015 Update 2) in combination with Python 2.7.11 and I'm unaware of =
any
> >>>> issue related to that.
> >>>>
> >>>> [1] http://www.luke1410.de/typo3/index.php?id=3D97
> >>> I cannot remember specific references now but when I looked into this
> >>> before it is because the official 2.x line is compiled using VC9.  Wh=
en
> >>> memory is passed between applications relying on different version of
> >>> the CRT then you can end up with hard to diagnose memory corruptions
> >>> that eventually cause problems.
> >> This is correct. If you are building a project linking in the CRT, you
> >> should ensure that all DLLs and libraries you build with use the same
> >> CRT. Mixing different CRT versions is unsupported and you will have
> >> undefined behavior. The possibilities for memory corruptions is the mo=
st
> >> prominent effect one might observe, but there are other problems/issue=
s
> >> this will cause too.
> >>> Digging a bit I found this thread [1] that highlights a similar CRT
> >>> issue in python modules such as psycopg2 (which I use for PostGreSQL)
> >>> that use the CRT internally...
> >>>
> >>> [1] https://groups.google.com/forum/#!topic/modwsgi/ATtKX6qWLXc
> >> As far as I  skimmed through the thread the problem here is not with
> >> python being compiled using VC9, but rather the module the python scri=
pt
> >> tries to load (psycopg2, which according to the web seems to be some
> >> postgre-sql-related library) was compiled with a different CRT than th=
e
> >> Apache binaries. That's a general issue, yes, and that's why I don't
> >> distribute the svn-apache modules with MaxSVN, even though they are
> >> built as part of the buildprocess (and utilized for testing). It's
> >> imperative that the CRT for the Apache modules matches the ones used t=
o
> >> build Apache and that only the distributor of the specific Windows
> >> Apache module can ensure.
> > ...and that is my problem: Trac is running under py2.7 (via mod_wsgi fr=
om
> > httpd) and using psycopg2 to connect to a PostGreSQL backend.  AFAIK, p=
ython
> > 2.7.x windows extensions should be built using VC++ 2008 to match the p=
ython
> > build, so it is best if I build httpd, mod_wsgi and svn using that comp=
iler
> > too (especially as local policy means I need to be able to apply the la=
test
> > e.g. OpenSSL updates as they come out).
>=20
> Certainly that's working. But since you are recompiling psycopg2
> yourself, why don't you just recompile that then using VS 2015? Or are
> there other python libs involved?

I am not compiling python or any of the support libs that we use, I decided=
 to compile httpd and svn instead.

I will have another go with VisualSVN again to see if it works for us now.

> --
> Regards,
> Stefan Hett