> The only race was for multiple processes simultaneously deciding they need
to create the (currently missing) file and then trying to open the file for
> write at the same time.
To what I see on the logs, this is not what I observe:
build 26-avr.-2013 13:11:12 CMake does not need to re-ru
On 04/29/2013 04:37 PM, Raffi Enficiaud wrote:
> - process 1 is accessing generate.stamp for reading
Nothing ever reads the file. Only its existence and modification
time matter.
> - process 2 is moving some "tmpfile" to generate.stamp -> race
The only race was for multiple processes simultaneo
I do not know the code that much, but I guess "Makefile::SetProjectName" is
called much earlier than
cmLocalVisualStudio7Generator::CreateVCProjBuildRule, right?
What do you think?
Best,
Raffi Enficiaud
-Original Message-----
From: Brad King [mailto:brad.k...@kitware.com]
Sent: lundi 29
On 04/29/2013 10:53 AM, Raffi Enficiaud wrote:
> I read the content of the change in the link you provided, and I have a
> newbie question:
> Why not using one timestamp (different filename) per library/binary/project?
The current approach evolved historically. A per-target approach would
proba
Hi,
I read the content of the change in the link you provided, and I have a
newbie question:
Why not using one timestamp (different filename) per library/binary/project
?
Looking forward to having this issue solved in the next official release!
Best,
Raffi Enficiaud
--
View this message in
On Wed, 2013-04-24 at 09:11 -0400, Paul Smith wrote:
> > I have seen this as well with the 2.8.11-rc releases. I am not exactly
> > what causes that.
>
> The package I'm trying to build is here, FWIW:
>
> https://github.com/nuodb/nuodb-php-pdo
>
> The CMakeLists.txt file is here:
>
> https://gi
On Wed, 2013-04-24 at 09:02 -0400, John Drescher wrote:
> > I installed it and it ran one time and I didn't see the error, but it's
> > intermittent so that's not definitive. Unfortunately one of my cmake
> > files failed (later on; this is a cmake file from a smaller
> > sub-project):
> >
> >
> I installed it and it ran one time and I didn't see the error, but it's
> intermittent so that's not definitive. Unfortunately one of my cmake
> files failed (later on; this is a cmake file from a smaller
> sub-project):
>
> CMake Error at CMakeLists.txt:190 (TARGET_LINK_LIBRARIES):
>
On Tue, 2013-04-23 at 21:50 -0400, Bill Hoffman wrote:
> On 4/23/2013 8:57 PM, J Decker wrote:
> > I've seen this also, and it is intermittant; once upon a time there were
> > several AV programs that held new files open too long, so subsequent
> > accesses would fail... sorry to be no help
> Can y
On Sun, Apr 21, 2013 at 12:32 AM, Paul Smith wrote:
> I looked up this message and found another report of this error which
> was purported to be fixed in cmake by this patch:
>
> commit 2dc17f88dd2de900154f153f521b803ec9b7c377
> Author: Brad King
> Date: 2013-02-12 10:46:22 -0500
For referenc
On 4/23/2013 8:57 PM, J Decker wrote:
I've seen this also, and it is intermittant; once upon a time there were
several AV programs that held new files open too long, so subsequent
accesses would fail... sorry to be no help
Can you try the current RC and see if it is fixed in that version of CMak
I've seen this also, and it is intermittant; once upon a time there were
several AV programs that held new files open too long, so subsequent
accesses would fail... sorry to be no help
On Tue, Apr 23, 2013 at 5:34 PM, Paul Smith wrote:
> On Tue, 2013-04-23 at 15:54 -0700, J Decker wrote:
> > do
On Tue, 2013-04-23 at 15:54 -0700, J Decker wrote:
> do you have antivirus software that you can disable?
No, there's no special antivirus software on these build servers. It's
hard to imagine what kind of issue antivirus software would cause, that
would be so intermittent. Our builds perform t
do you have antivirus software that you can disable?
On Tue, Apr 23, 2013 at 2:43 PM, Paul Smith wrote:
> On Sun, 2013-04-21 at 00:32 -0400, Paul Smith wrote:
> > Hi all; I'm getting this error most, but not every, time I run cmake on
> > my main Windows build system:
> >
> > 28>CUSTOMBUILD : C
On Sun, 2013-04-21 at 00:32 -0400, Paul Smith wrote:
> Hi all; I'm getting this error most, but not every, time I run cmake on
> my main Windows build system:
>
> 28>CUSTOMBUILD : CMake error : Cannot restore timestamp
> D:\build-dir\MASTER-BRANCHES30-WINDOWS\BaseTest\CMakeFiles\generate.stamp
>
Hi all; I'm getting this error most, but not every, time I run cmake on
my main Windows build system:
28>CUSTOMBUILD : CMake error : Cannot restore timestamp
D:\build-dir\MASTER-BRANCHES30-WINDOWS\BaseTest\CMakeFiles\generate.stamp
It happens for different targets as well, not always the same on
16 matches
Mail list logo