On 10.09.2015 19:33, Asa Packer wrote:
> I looked at this a bit more, and it looks like in 1.9.1 the
> svnversion EXE and the SVN DLL's may have gotten statically linked
> with the C runtime. I've attached screenshots of Dependency Walker
> applied to the 1.9.0 and 1.9.1 versions of svnversion.exe and there's
> quite a difference.
>
> In https://msdn.microsoft.com/en-us/library/abx4dbyh.aspx it says
> that "Because a DLL built by linking to a static CRT will have its
> own CRT state, it is not recommended to link statically to the CRT in
> a DLL unless the consequences of this are specifically desired and
> understood." I don't know specifically what they mean, but maybe
> this is related to the behavior I'm seeing.
Yes, the problem is because of the static linking with the CRT.
Not sure how I can fix this though, not even sure if it's even possible.
Problem is: going back to dynamically linking with the CRT is not an
option either: the x64 merge modules for the c-runtime and MFC are
completely broken and must not be used.
Strange thing: I've reported the problem to MS, and the issue was open
for a while. Now when I wanted to check it again, it is not there
anymore ("The content that you requested cannot be found or you do not
have permission to view it.").
https://connect.microsoft.com/VisualStudio/feedback/details/1639267/c-runtime-and-mfc-merge-modules-for-x64-are-broken-install-to-syswow64-instead-of-system32
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest interface to (Sub)version control
/_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=3137109
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2015-09-12 02:50:54 CEST