Re: License compliance on updating gcc runtime libraries

2019-02-28 Thread hiraku.toyooka
> Note that nobody can give you definitive answers to questions like this > since they haven't been litigated. So any answer is an "educated guess". Yes. I understand I cannot get definitive answers for license interpretation. > My view is that it's both, depending on the context. Remember that

Re: License compliance on updating gcc runtime libraries

2019-02-28 Thread hiraku.toyooka
Thank you for your reply. > The exception applies to the application code, not to libgcc_s.so, > libstdc++.so etc. I noticed my prerequisite might be wrong. I thought that the shared runtime libraries are also included in the "work of Target Code formed by combining the Runtime Library with Indep

Re: License compliance on updating gcc runtime libraries

2019-02-27 Thread Simon Wright
On 27 Feb 2019, at 18:37, Richard Kenner wrote: > > 1) Whether executing a program is considered making a copy under > copyright law. I had a look through some of the published judgements, and it's clear that in the US at least copying into RAM (for whatever purpose, and provided the copy has

Re: License compliance on updating gcc runtime libraries

2019-02-27 Thread Richard Kenner
> That depends on your local copyright law. Some, like the US, have > language saying that copies necessary for usual operation are *not* > covered under copyright. I'm refering to US law. Where, precisely, is the language you are referring to? Note that there are two separate issues: (1) Wheth

Re: License compliance on updating gcc runtime libraries

2019-02-27 Thread Zan Lynx
On 2/27/19 6:20 AM, Richard Kenner wrote: > That's actually not extreme, but pretty accepted. And yes, that has > been litigated. And you can see that in the GPL in the definition of > "propagate": the exclusion of executing it on a computer wouldn't be > necessary if that weren't considered a co

Re: License compliance on updating gcc runtime libraries

2019-02-27 Thread Richard Kenner
> Remember that, from the perspective of copyright law, executing a > program is making a "copy" > of that program. > > Has that (rather extreme) view been litigated? That's actually not extreme, but pretty accepted. And yes, that has been litigated. And you can see that in the G

Re: License compliance on updating gcc runtime libraries

2019-02-27 Thread Simon Wright
On 27 Feb 2019, at 12:41, Richard Kenner wrote: > > Remember that, from the perspective of copyright law, executing a program is > making a "copy" > of that program. Has that (rather extreme) view been litigated?

Re: License compliance on updating gcc runtime libraries

2019-02-27 Thread Richard Kenner
> I have questions about the GCC Runtime Library Exception. Note that nobody can give you definitive answers to questions like this since they haven't been litigated. So any answer is an "educated guess". Having said that ... > When an equipment vendor distributes an update of shared gcc runtime

Re: License compliance on updating gcc runtime libraries

2019-02-27 Thread Jonathan Wakely
On Wed, 27 Feb 2019 at 09:06, wrote: > > Hello, > > I have questions about the GCC Runtime Library Exception. > > When an equipment vendor distributes an update of shared gcc runtime > libraries (e.g. libgcc_s.so, libstdc++.so) to the shipped equipment > and when the equipment has applications whi

License compliance on updating gcc runtime libraries

2019-02-27 Thread hiraku.toyooka
Hello, I have questions about the GCC Runtime Library Exception. When an equipment vendor distributes an update of shared gcc runtime libraries (e.g. libgcc_s.so, libstdc++.so) to the shipped equipment and when the equipment has applications which are dynamically linked to older release of the sh