On 17.11.2020 13:53, Uwe Klaus wrote:
On Mon, 16 Nov 2020, Bodie wrote:
original questions is now nearly one year old
https://mail-index.netbsd.org/pkgsrc-users/2019/12/10/msg029983.html
There was no response and I can confirm that problem still exists on
9.1 stable amd64 and evbarm. Are de
Hello,
unfortunately I am not yet able to figure out what's wrong.
I think there is something wrong with OpenJDK11 port for netbsd or some
OS feature that it relies on, does not work as JDK 11 expects.
I do not think there is a problem with Gradle, at all.
I have tried Gradle 6.7 and the old 5
I just ran into it independently on NetBSD/amd64 current 9.99.x.
On 20.11.2020 02:59, ts1000 wrote:
> Hello,
> wanted to bump up my question to see if anybody could help.
> Also, if I may, I wanted to ask if this group is the right question
> about using NetBSD as a development environment (using
ts1000 writes:
> It seems that gradle is:
> placing a lock on a file somewhere in ~/.gradle directory
> then, I presume it writes to it.
>
> Then it tries to remove the lock, and then close the file.
>
> Somewhere there there seem to be an error.
That sounds promising.
> There is also an error
On 21.11.2020 19:59, ts1000 wrote:
Greg, Bodie
thank you for suggesting to look for ktrace.out, after running:
ktrace -i gradle status
Indeed the dump was there. Now I know how to use ktrace, at least
supreficially.
I ran kdump on it, got an ASCII and started looking for abnormalities.
On 21.11.2020 19:59, ts1000 wrote:
Greg, Bodie
thank you for suggesting to look for ktrace.out, after running:
ktrace -i gradle status
Indeed the dump was there. Now I know how to use ktrace, at least
supreficially.
It's not a Linux. It's a BSD. Everything is in the system without need
Greg, Bodie
thank you for suggesting to look for ktrace.out, after running:
ktrace -i gradle status
Indeed the dump was there. Now I know how to use ktrace, at least
supreficially.
I ran kdump on it, got an ASCII and started looking for abnormalities.
It seems that gradle is:
placing a lock