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

Re: TSVNCache might cause 'permission denied' error for 'precompiled header' in VC 6

From: V.S. <john_v_doe_at_yahoo.com>
Date: 2006-06-18 14:46:59 CEST

Jiaji Wu <cola.is.knowbuddy <at> gmail.com> writes:

> Dear Developer(s), Recently I always get 'fatal error C1083:
> Cannot open precompiled header file: 'Release/x.pch': Permission
> denied' kinda error while building project using Visual C ++ 6.0
> sp6 ( with Visual Assist plugin ). I have
> to try several times before building ok, and it really troubles
> me a lot. I accidentally found that TSVNCache.exe might be the
> cause of the problem. If I kill it brutally using task manager
> before building, I got no error!

I'm observing very similar behavior over here : eVC4 SP4 (Microsoft
Embedded Visual C++ 4) repeatedly fails to build a rather large
workspace (~80 projects, ~1200 files, ~150 dirs), complaining that it
can't access some files (most often it's the equivalent of "C1083"
Jiaji Wu descrived above, but sometimes eVC4 whines about being unable
to access some temporary files it creates for internal purposes). In
order to successfully build the entire workspace I have to repeatedly
force eVC4 to keep building, up to a hundred times per build cycle
(read : grrr!).

Cursory investigation seems to indicate that the only executables
accessing the files/directories of interest during the build are eVC4,
eVC4-spawned tasks (e.g. compiler) and TSVNCache.

In my case the problem seems to have appeared after I upgraded from
TortoiseSVN 1.2.6 build 4786 to TortoiseSVN 1.3.4 build 6692.

Any ideas?

Thanks in advance,

V. Solo.

Client :
WinXP Pro, SP2.
Subversion 1.2.3 (r15833) & TortoiseSVN 1.3.4 build 6692

To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sun Jun 18 14:50:24 2006

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

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