From: Mark Evans (evans_mark_at_[hidden])
Date: 2006-02-16 06:55:46
Yesterday, I stumbled on a problem where rule MkDir1 tried and failed to create a directory that already existed. This was in trying to build a library with toolset gcc with os = CYGWIN after having built it with other toolsets. I don't know what I did, but not I cannot replicate the problem this morning. Must be change in the phase of the moon. Nevertheless, would it hurt to add a defensive -p flag to mkdir in tools/common.jam so that it won't fail when it mistakenly tries to create a directory that already exists? I recall someone complaining about this with Perforce jam.
RCS file: /cvsroot/boost/boost/tools/build/v2/tools/common.jam,v
retrieving revision 1.45
diff -u -r1.45 common.jam
--- common.jam 15 Dec 2005 18:04:05 -0000 1.45
+++ common.jam 16 Feb 2006 11:42:00 -0000
@@ -528,7 +528,7 @@
- mkdir "$(<)"
+ mkdir -p "$(<)"
actions piecemeal together existing Clean
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk