From: Jan Nieuwenhuizen <janneke-list@xs4all.nl>
To: guile-devel <guile-devel@gnu.org>
Subject: build error: race problem in mkdir?
Date: Wed, 16 Mar 2011 20:42:43 +0100 [thread overview]
Message-ID: <1300304563.12298.363.camel@vuurvlieg> (raw)
I got the error below building today's stable-2.0.
It seems that ensure-writable-dir in compile.scm can
be raced.
Greetings,
Jan.
guile-tools compile -Wunbound-variable -Warity-mismatch -Wformat -o "oop/goops/composite-slot.go" "/home/janneke/vc/gub/target/tools/src/guile-2.0.0.1/module/oop/goops/composite-slot.scm"
Backtrace:
In ice-9/boot-9.scm:
170: 9 [catch #t #<catch-closure 977da80> ...]
In unknown file:
?: 8 [catch-closure]
In ice-9/boot-9.scm:
62: 7 [call-with-prompt prompt0 ...]
In ice-9/eval.scm:
389: 6 [eval # #]
350: 5 [eval # #]
In unknown file:
?: 4 [for-each #<procedure 9948c30 at ice-9/eval.scm:378:13 (a)> #]
In ice-9/eval.scm:
350: 3 [eval # #]
434: 2 [lp (#<fluid 20>) ("")]
In system/base/compile.scm:
128: 1 [compile-file "/home/janneke/vc/gub/target/tools/src/guile-2.0.0.1/module/oop/goops.scm" ...]
In unknown file:
?: 0 [mkdir "oop" #<undefined>]
ERROR: In procedure mkdir:
ERROR: In procedure mkdir: File exists
make[2]: *** [oop/goops.go] Error 1
make[2]: *** Waiting for unfinished jobs....
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl
next reply other threads:[~2011-03-16 19:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 19:42 Jan Nieuwenhuizen [this message]
2011-03-29 9:40 ` build error: race problem in mkdir? Andy Wingo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1300304563.12298.363.camel@vuurvlieg \
--to=janneke-list@xs4all.nl \
--cc=guile-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).