Building hsdis?

Andrew Haley aph at redhat.com
Wed Jan 3 14:14:32 UTC 2018


On 03/01/18 14:02, Florian Weimer wrote:
> On 01/03/2018 02:58 PM, Andrew Haley wrote:
>> On 03/01/18 13:35, Florian Weimer wrote:
>>> On 12/25/2017 11:58 PM, Andrew Haley wrote:
>>>> IANAL, but AFAIK It would not help.  The incompatibility is because
>>>> you can't link pure GPLv2 code (HotSpot) and pure GPLv3 code
>>>> (binutils) together, even via dynamic linkage.  Changing the licences
>>>> of hsdis.{c,h}) won't solve that problem.
>>>
>>> But Hotspot links against libgcc and libstdc++, which are GPLv3 as well,
>>> so that issue isn't specific to hsdis.
>>
>> No, they are not.  They never have been.
> 
> The header file comments and the exception itself say otherwise.
> 
>> https://www.gnu.org/licenses/gcc-exception-3.1-faq.en.html
> 
> The exception gives permission to ignore certain terms imposed by the 
> GPLv3 (“even if such propagation would otherwise violate the terms of 
> GPLv3”).  It does not give permission to violate the terms of the GPLv2, 
> and it could not, because the GPLv2 part of the overall conglomerate is 
> an unrelated project with a different copyright holder.

Of course not.  The question is nothing to do with that.  The problem
is that pure GPLv2 and pure GPLv3 are not compatible.  (AFAIK, IANAL,
etc.)  Nobody ever intended that libgcc, for example, should be
incompatible with pure GPLv2 programs.

-- 
Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671


More information about the build-dev mailing list