Somehow making this depend on the use of configure feels wrong,
since we tried to keep that config.mak.gen built by configure
strictly optional. In other words, I think the result of your
patch should be buildable with or without ./configure in a
separate directory if we are going to do this.
Care to explain why it is too cumbersome to handle without
./configure magic?
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html