[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Problem building trunk on Windows

From: Mark Phippard <mphippard_at_collab.net>
Date: Mon, 22 Dec 2008 12:13:26 -0500

On Mon, Dec 22, 2008 at 12:11 PM, Stefan K√ľng <tortoisesvn_at_gmail.com> wrote:
> Mark Phippard wrote:
>> On Mon, Dec 22, 2008 at 12:02 PM, Mark Phippard <markphip_at_gmail.com> wrote:
>>> It could be related to that. Even though I have the SDK installed, I
>>> recall I had problems where I had to make the VC98 version come before
>>> it in my LIB path to do a clean build. I just tried commenting that
>>> out, so that the SDK path comes first. I still get an error, but now
>>> it is a new error:
>>> Performing Custom Build Step on ..\..\..\build\generator\extractor.py
>>> Compiling resources...
>>> Compiling...
>>> empty.c
>>> Linking...
>>> .\libsvn_subr.def : warning LNK4087: CONSTANT keyword is obsolete; use DATA
>>> Creating library ..\..\..\Release\subversion\libsvn_subr/libsvn_subr-1.lib an
>>> d object ..\..\..\Release\subversion\libsvn_subr/libsvn_subr-1.exp
>>> uuid.lib(mlang_i.obj) : fatal error LNK1103: debugging information corrupt; reco
>>> mpile module
>>> Error executing link.exe.
>>> So I suspect that the VC98 SDK includes the crypt32.lib but has an
>>> older version without those symbols in it. I will try to Google
>>> around about this latest problem with uuid.lib.
>> This looks telling:
>> http://www.tech-archive.net/Archive/VC/microsoft.public.vc.atl/2005-08/msg00265.html
>> It sounds like the latest SDK's do not work with MSVC 6. Crap. I
>> wonder how I will ever get my hands on an old SDK if this is true?
> The latest SDK that still works with VC6 is the one from february 2003
> [1]. All later SDKs won't work anymore with VC6.
> But why are you still using VC6? The VCExpress [2] is free and has the
> latest compiler which works with the latest SDK without any problems.

I have a VS 2008 license too. That is not a problem. I use MSVC 6
because that is still what we use for our "official" binaries due to
the Apache dependency. I also use the binaries I build in Subclipse
and if I compile with a newer version than I have to deal with
distributing the new MSVCRT DLL's which I do not want to have to deal

Mark Phippard
Received on 2008-12-22 18:13:45 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.