How does GPL affect a Makefile-only modification?
<p>As a continuation of <a href="https://law.stackexchange.com/questions/45797/gpl-does-changing-makefiles-and-configurations-considered-as-modifications">this question</a>, does a Makefile modification when building GPL source mean my own program becomes GPL also ? For example, if some third-party GPL'd source contains exit(), and I add to the Makefile -Derror_handling=exit and link an error_handling() function that performs error handling and returns without exiting, does that count as a GPL modification ?  I could also change link order and supply my own exit() function to achieve the same result, would that count as a GPL modification ?</p>

<p>Your program doesn’t “become GPL” at all. That’s not how GPL works.</p>
<p>The GPL license gives you two permissions without any obligation: You are allowed to use the software, and you are allowed to modify the software and use the modified software. If the software is a combination of GPL licensed and your own software, then your own software is not GPL licensed.</p>
<p>The GPL license only comes into play when you distribute it (hand a copy to someone else), with or without your software added.</p>
<p>You then have the choice: Either you ship the complete software under the GPL license and everything is legally fine, or you ship it without the GPL license which makes it copyright infringement. It’s your choice. Changing the make file does nothing to the license, you have to do that yourself. Of course when I say “choice” is like leaving a store with goods, you have the choice to pay or become a thief. It doesn’t mean it’s legal, it isn’t.</p>

licensing open-source-software gpl