Michael Wild wrote:
> the dependency should prevent anything bad from happening.
Dependencies in the actual "Makefile" are not meaningful. It is
a front-end that launches a make process for driving the build
through "CMakeFiles/Makefile2" which has the real inter-target
dependencies. Each target
I don't really see why this should be a problem. If "install" depends on "all",
everything should be fine, even in the parallel case (otherwise the
dependency-tracking is seriously broken). Even if "all" is the ".DEFAULT"
target, make should ignore that because I explicitly specified the target
Hi Michael,
This is a well-known problem with parallel make. When using -j you
should NEVER specify multiple targets, because each target could be
built independently in a separate make process even if they have
dependencies. Here, you're using the implicit target 'all' and the
target 'install'. T
Hi all
While creating a formula for Homebrew on Mac OS X 10.6.2 I happened across a
problem when I tried to build CMake 2.8.1 in parallel (-j2) and directly
invoked the "install" target where libcmsys.a and libCMakeLib.a get built
twice. I.e. I did the following:
$ /bootstrap --prefix= --syste
