5 ms·

anything compiled using the GNU compiler would be also under the GNU (since you would be compiling libraries from this compiler straight into your application/b

anything compiled using the GNU compiler would be also under the GNU (since you would be compiling libraries from this compiler straight into your application/binary and calling function names There is an explicit exception in the GCC licensing to allow compiled programs incorporating GCC runtime code to be distributed under any license the author wishes. You can read more about this topic at http://www.gnu.org/licenses/gcc-exception-faq.html http://www.gnu.org/licenses/gcc-exception-faq.html The compiled program is in fact a derivative work of the incorporated libraries and it is only this explicit exception which allows for the greater work to be redistributed under another license.

0bfusct3 16y ago
Then taking it all the way down to the hardware, every user of x86 should be required to agree to a license agreement to use an x86 processor since it 'interprets' opcodes on-the-fly thus everything that uses x86 is under an intel license QED. I don't know the full details of the thesis theme but use an API doesn't constitute violation of the GPL v2 - see: tivo and thousands of routers, wireless cards, etc.
- quadhome 16y ago
  The are multiple licenses for the x86 ISA. And companies that produce common chipsets specifically allow open development on top of them. They make more money that way. This wasn't always the case, though. It's easy to forget history.
  - 0bfusct3 16y ago
    My example may have been flawed (it was meant for exaggeration ) but the point still remains that API use is fine under GPL v2.
    - chopsueyar 16y ago
      I assume you have successfully litigated this position in a US court on multiple occasions?
- noste 16y ago
  Tivo has released sources for the GPL covered portions of its software (http://www.tivo.com/linux/index.html http://www.tivo.com/linux/index.html ). At least some router manufacturers have also released source code as required by the GPL. For example, see D-Link http://tsd.dlink.com.tw/GPL.asp http://tsd.dlink.com.tw/GPL.asp and Cisco http://homesupport.cisco.com/en-us/gplcodecenter http://homesupport.cisco.com/en-us/gplcodecenter .
  - 0bfusct3 16y ago
    Tivo releases what they see as either not a competitive advantage or a burden to maintain. Just like Nvidia releases the shim but nothing relating the how the hardware works - it's a business they aren't here to plant daisies in the FOSS fields there here to make a bottom line.

0bfusct3 16y ago

Then taking it all the way down to the hardware, every user of x86 should be required to agree to a license agreement to use an x86 processor since it 'interprets' opcodes on-the-fly thus everything that uses x86 is under an intel license QED. I don't know the full details of the thesis theme but use an API doesn't constitute violation of the GPL v2 - see: tivo and thousands of routers, wireless cards, etc.

quadhome 16y ago
The are multiple licenses for the x86 ISA. And companies that produce common chipsets specifically allow open development on top of them. They make more money that way. This wasn't always the case, though. It's easy to forget history.
- 0bfusct3 16y ago
  My example may have been flawed (it was meant for exaggeration ) but the point still remains that API use is fine under GPL v2.
  - chopsueyar 16y ago
    I assume you have successfully litigated this position in a US court on multiple occasions?
noste 16y ago
Tivo has released sources for the GPL covered portions of its software (http://www.tivo.com/linux/index.html http://www.tivo.com/linux/index.html ). At least some router manufacturers have also released source code as required by the GPL. For example, see D-Link http://tsd.dlink.com.tw/GPL.asp http://tsd.dlink.com.tw/GPL.asp and Cisco http://homesupport.cisco.com/en-us/gplcodecenter http://homesupport.cisco.com/en-us/gplcodecenter .
- 0bfusct3 16y ago
  Tivo releases what they see as either not a competitive advantage or a burden to maintain. Just like Nvidia releases the shim but nothing relating the how the hardware works - it's a business they aren't here to plant daisies in the FOSS fields there here to make a bottom line.