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) a
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
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
>> o
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 Hotspo
On 29/12/17 20:09, Mario Torre wrote:
> 2017-12-29 17:16 GMT+01:00 Volker Simonis :
>
>> So than why aren't you reluctant about using hsdis itself? Or did you
>> (or your co-workers) never ever used any hsdis version based on
>> binutils > 2.17, released in June 2006 (small hint: aarch64 support
>
2017-12-29 17:16 GMT+01:00 Volker Simonis :
> So than why aren't you reluctant about using hsdis itself? Or did you
> (or your co-workers) never ever used any hsdis version based on
> binutils > 2.17, released in June 2006 (small hint: aarch64 support
> was added in binutils 2.23 around 2012 and i
On Thu, Dec 28, 2017 at 11:48 AM, Andrew Haley wrote:
> On 27/12/17 11:26, Volker Simonis wrote:
>> There are two different problems here:
>>
>> 1. It is not possible to build and redistribute hsdis.so because of
>> GPLv2 and GPLv3 license incompatibilities.
>>
>> This problem could be easily solv
On 27/12/17 11:26, Volker Simonis wrote:
> There are two different problems here:
>
> 1. It is not possible to build and redistribute hsdis.so because of
> GPLv2 and GPLv3 license incompatibilities.
>
> This problem could be easily solved by re-licensing hsdis.{c,h} under
> GPLv3. That would allo
On Mon, Dec 25, 2017 at 11:58 PM, Andrew Haley wrote:
> On 24/12/17 12:16, Volker Simonis wrote:
>> Andrew Haley schrieb am So. 24. Dez. 2017 um 09:27:
>>
>>> On 23/12/17 17:02, Volker Simonis wrote:
Andrew Haley schrieb am Sa. 23. Dez. 2017 um 12:25:
>>>
>>> The GB can only solve problems
On 24/12/17 12:16, Volker Simonis wrote:
> Andrew Haley schrieb am So. 24. Dez. 2017 um 09:27:
>
>> On 23/12/17 17:02, Volker Simonis wrote:
>>> Andrew Haley schrieb am Sa. 23. Dez. 2017 um 12:25:
>>
>> The GB can only solve problems which, in principle, can be solved. I
>> know of no reasonabl
On Sun, Dec 24, 2017 at 11:22 PM, Mario Torre
wrote:
>> builds hsdis violates the GNU license because he
>> combines GPLv2 with GPLv3 code
>
> Are those files GPL 2 only or “at your option any later version” too?
>
They are GPLv2 only, otherwise there wouldn't be a problem.
> Indeed, GPL v2 and
> builds hsdis violates the GNU license because he
> combines GPLv2 with GPLv3 code
Are those files GPL 2 only or “at your option any later version” too?
Indeed, GPL v2 and v3 are not compatible, but if the upgradability is
allowed then the effective version is already 3. The rest of the openjdk
Andrew Haley schrieb am So. 24. Dez. 2017 um 09:27:
> On 23/12/17 17:02, Volker Simonis wrote:
> > Andrew Haley schrieb am Sa. 23. Dez. 2017 um 12:25:
> >
> >> On 20/12/17 09:54, Volker Simonis wrote:
> >>> Yes, that's exactly the issue. And it was communicated to the OpenJDK
> >>> Governing Boa
On 23/12/17 17:02, Volker Simonis wrote:
> Andrew Haley schrieb am Sa. 23. Dez. 2017 um 12:25:
>
>> On 20/12/17 09:54, Volker Simonis wrote:
>>> Yes, that's exactly the issue. And it was communicated to the OpenJDK
>>> Governing Board more than two and a half years ago (see my mail
>>> "Providing
Andrew Haley schrieb am Sa. 23. Dez. 2017 um 12:25:
> On 20/12/17 09:54, Volker Simonis wrote:
> > Yes, that's exactly the issue. And it was communicated to the OpenJDK
> > Governing Board more than two and a half years ago (see my mail
> > "Providing 'hsdis' binaries not possible because of GPLv
On 20/12/17 09:54, Volker Simonis wrote:
> Yes, that's exactly the issue. And it was communicated to the OpenJDK
> Governing Board more than two and a half years ago (see my mail
> "Providing 'hsdis' binaries not possible because of GPLv2/GPLv3
> license clash" from May 2015 [1]) and since then rei
Hi Ted!
For Windows, I have found the instructions listed here to be the most
helpful:
https://dropzone.nfshost.com/hsdis.htm
I recommend building on Cygwin as described above. You will need the
MinGW packages installed in your Cygwin environment (also described in
the above post).
We rea
OK, built flawlessly.
Couple of notes:
(*) When I tried to do "make both", as mentioned in the README, it failed in
the configure step: "C compiler cannot create executables". This was after
"make all64" worked flawlessly. (Both have the BINUTILS variable set via the
command-line; I'm eliding
ear - however with very little hope that it
will be resolved :(
Regards,
Volker
[1] http://mail.openjdk.java.net/pipermail/discuss/2015-May/003754.html
> Cheers,
> -Buck
>
>
> On 2017/12/20 18:35, Ted Neward wrote:
>>
>> Sorry--I was cribbing from here
>> (ht
pain point and are looking to improve things in the future. It
is simply a matter of bandwidth at the moment.
Cheers,
-Buck
On 2017/12/20 18:35, Ted Neward wrote:
Sorry--I was cribbing from here
(https://www.chrisnewland.com/building-hsdis-on-linux-amd64-on-debian-369) and
it references using
Sorry--I was cribbing from here
(https://www.chrisnewland.com/building-hsdis-on-linux-amd64-on-debian-369) and
it references using 2.23, which memory transposed to 2.32, I think.
I'm not sure what was going wrong (well, I can tell you what the errors were,
but I dunno what was causing
Hi Ted!
> the version of binutils (I was using 2.32)
Not sure what that is. Latest binutils is 2.29.1.
> I was doing make BINUTILS= ARCH=amd64
That should also work, but I'd still keep things simple and just specify
the "all64" make target. As always, whatever is documented in the README
fil
I will give this a shot tomorrow; I can see two things already that I did that
was different, the version of binutils (I was using 2.32) and the make command
(I was doing make BINUTILS= ARCH=amd64 from the hsdis directory
itself inside the jdk source. Do I need to clone the hs repo on its own? O
Hi Ted!
No blog to point you to, but building on non-Windows platforms should be
pretty painless these days.
> then tried again with the JDK source
Yes, that is the one to use. The makefile had a number of issues that I
fixed recently but have not (yet) backported to 8u-dev.
I was able to
Hey, all. Been trying for a day and a half now to build the hsdis disassembly
plugin in jdk/src/utils/hsdis, with no luck. (Tried first off of the JDK8u
source, then tried again with the JDK source, no love either way.)
Is there a definitive page (wiki, blog, etc) that describes how to build
25 matches
Mail list logo
