Separate IR targets to avoid build failure
Separate IR targets to avoid build failure

When executing custom commands / custom targets in parallel, the
dependency resolution for these targets will happen in parallel as
well. If two custom targets are started sufficiently close together for
a clean build, each of the target will execute all dependencies. In the
worst case, both targets will try to overwrite files the other target
has already written leading to either corrupt archives or missing code.

Some background can be found here:
http://www.cmake.org/pipermail/cmake/2011-July/045256.html

This patch separates the two IR targets and moves them to the end of the
compile chain.

Change-Id: I5b26ebd1c3421788fd22e6a09ef96dd6b944e89e
Reviewed-on: http://gerrit.cloudera.org:8080/318
Reviewed-by: Martin Grund <2546548d516fa64c411fde8242af35f3f80ad31f@cloudera.com>
Tested-by: Internal Jenkins

ibmsoe/ImpalaPPC,ibmsoe/ImpalaPPC,ibmsoe/ImpalaPPC,ibmsoe/ImpalaPPC,ibmsoe/ImpalaPPC,ibmsoe/ImpalaPPC,ibmsoe/ImpalaPPC