Consider:
foo.c foo.h: foo.in
some-tool foo.in
If you have some targets that depend on foo.c and other targets that depend on foo.h and you build in parallel, some-tool will run twice, possibly at the same time as something is reading the output, possibly causing problems.
[edit]
The workaround I've used is something like:
foo.c: foo.in
some-tool foo.in
foo.h: foo.c
true
Note that the "true" command is important because GNU make will search a library of implicit rules if you have no recipes for a particular target.
In general multiple output files are even harder with some make replacements, because most make replacements try to be smarter about build outputs. redo, for example cannot handle this, but tup can.