Different license statements in different files

[jere-software]

I recently cloned the community-2018 branch, pulled, built, and installed the zfp runtime for the sam4s following the instructions in the README.md file. When I viewed the files in the installed runtime, I noticed that most files (system.ads for example) did in fact include the runtime link exception in the license:

-- As a special exception under Section 7 of GPL version 3, you are granted --
-- additional permissions described in the GCC Runtime Library Exception, --
-- version 3.1, as published by the Free Software Foundation. --

However, some of the files (s-secsta.ads) did not specify the runtime exception. It actually looks intentionally removed (lots of blank space). It still has the blurb saying I should have received the COPYING.RUNTIME file but the file license blurb does not say that it applies to the files in question.

It appears that linking against the zfp runtime makes your entire application under the full GPL3 without the linking exception?

This affects multiple files. I don't know if it affects multiple boards.

Either way, the license statements should be more consistent probably?

[Fabien-Chouteau]

Hi @jeremiahbreeden ,

However, some of the files (s-secsta.ads) did not specify the runtime exception. It actually looks intentionally removed (lots of blank space). It still has the blurb saying I should have received the COPYING.RUNTIME file but the file license blurb does not say that it applies to the files in question.

The run-times in the GNAT Community releases are indeed provided under GPL3 without GCC Runtime Library Exception.

The source files in this repository are provided under GPL3 with GCC Runtime Library Exception.

When you compile a run-time/BSP from this repository, sources from GNAT Community are mixed with sources from the repository. This is why the resulting run-time has mixed licenses.

It appears that linking against the zfp runtime makes your entire application under the full GPL3 without the linking exception?

That is right, the linking exception doesn't apply with GNAT Community release. The rational is that GNAT community is meant for evaluation and open source development.

Regards,

[jere-software]

Okies. Thank you for the response. I close this then.

As a relative newbie to embedded Ada, that surprised me.