When to set / keep MAKE_JOBS_UNSAFE?

2020-10-10 Thread Moritz Schmitt
Hi, I recently took over maintainership of devel/gindent, and I'm in the process of cleaning it up. In its Makefile MAKE_JOBS_UNSAFE is set and I'm trying to figure out if it's acutally needed or not. Subversion's log has the following entry: r244490 | pav | 2009-11-20 00:41:55 +0100 (Fr

Re: When to set / keep MAKE_JOBS_UNSAFE?

2020-10-10 Thread Kurt Jaeger
Hi! > In its Makefile MAKE_JOBS_UNSAFE is set and I'm trying to figure out if > it's acutally needed or not. If you build it on a box with more CPUs cores, will it fail or not ? What number of CPUs cores did you try ? I've just tried it without MAKE_JOBS_UNSAFE on a 32 and it built fine. So I g

Re: When to set / keep MAKE_JOBS_UNSAFE?

2020-10-10 Thread Moritz Schmitt
Kurt Jaeger (Oct 10, 2020): > > In its Makefile MAKE_JOBS_UNSAFE is set and I'm trying to figure out if > > it's acutally needed or not. > > If you build it on a box with more CPUs cores, will it fail or not ? > > What number of CPUs cores did you try ? I built it successfully on FreeBS

OpenJDK ports and 13-CURRENT

2020-10-10 Thread Shawn Webb
Hey all, It appears the latest import of llvm 11.0.0 breaks the OpenJDK 12 and above ports. Is anyone tracking this breakage? Thanks, -- Shawn Webb Cofounder / Security Engineer HardenedBSD GPG Key ID: 0xFF2E67A277F8E1FA GPG Key Fingerprint: D206 BB45 15E0 9C49 0CF9 3633 C85B 0AF8 AB

Re: OpenJDK ports and 13-CURRENT

2020-10-10 Thread Dimitry Andric
On 10 Oct 2020, at 21:03, Shawn Webb wrote: > It appears the latest import of llvm 11.0.0 breaks the OpenJDK 12 and > above ports. Is anyone tracking this breakage? Define "break". :) I can't find any PR, so I don't think so. The latest builds on the ports cluster seem to have succeeded, but even

Re: OpenJDK ports and 13-CURRENT

2020-10-10 Thread Shawn Webb
On Sat, Oct 10, 2020 at 09:18:08PM +0200, Dimitry Andric wrote: > On 10 Oct 2020, at 21:03, Shawn Webb wrote: > > It appears the latest import of llvm 11.0.0 breaks the OpenJDK 12 and > > above ports. Is anyone tracking this breakage? > > Define "break". :) I can't find any PR, so I don't think s

Re: OpenJDK ports and 13-CURRENT

2020-10-10 Thread Dimitry Andric
On 10 Oct 2020, at 21:23, Shawn Webb wrote: > > On Sat, Oct 10, 2020 at 09:18:08PM +0200, Dimitry Andric wrote: >> On 10 Oct 2020, at 21:03, Shawn Webb wrote: >>> It appears the latest import of llvm 11.0.0 breaks the OpenJDK 12 and >>> above ports. Is anyone tracking this breakage? >> >> Defin

Re: OpenJDK ports and 13-CURRENT

2020-10-10 Thread Shawn Webb
On Sat, Oct 10, 2020 at 09:45:58PM +0200, Dimitry Andric wrote: > On 10 Oct 2020, at 21:23, Shawn Webb wrote: > > > > On Sat, Oct 10, 2020 at 09:18:08PM +0200, Dimitry Andric wrote: > >> On 10 Oct 2020, at 21:03, Shawn Webb wrote: > >>> It appears the latest import of llvm 11.0.0 breaks the Open

Re: OpenJDK ports and 13-CURRENT

2020-10-10 Thread Thierry Thomas
Le sam. 10 oct. 20 à 21:49:26 +0200, Shawn Webb écrivait : > > Ah, that is -fno-common fallout, strange that there is no build breakage > > reported in the FreeBSD ports build cluster? > > > > From gcc 10 and clang 11 onwards, -fno-common is the default (this is > > really a historical mistake,

Re: FreeBSD Port: telegram-desktop-2.3.2 videocalls

2020-10-10 Thread Henry Hu
Okay, it seems like that there's a DCHECK related to threading. However, if I disable the DCHECKs, video call seems to work. It's not ideal, as typically these should not fail. But for now, I'll just send a patch to disable it. Would you please file a problem report so we can follow up there? On T

Re: OpenJDK ports and 13-CURRENT

2020-10-10 Thread Dimitry Andric
On 10 Oct 2020, at 21:49, Shawn Webb wrote: > > On Sat, Oct 10, 2020 at 09:45:58PM +0200, Dimitry Andric wrote: >> On 10 Oct 2020, at 21:23, Shawn Webb wrote: ... >>> Log of the HardenedBSD 13-CURRENT/amd64 package >>> build:http://ci-03.md.hardenedbsd.org/data/hardenedbsd-13_amd64-local/2020-10

Re: OpenJDK ports and 13-CURRENT

2020-10-10 Thread Yasuhiro KIMURA
From: Dimitry Andric Subject: Re: OpenJDK ports and 13-CURRENT Date: Sun, 11 Oct 2020 00:57:33 +0200 > Can you try the attached patch? I haven't yet looked at openjdk 13 and > up, but I assume they will need at least the XSynchronize fix, and maybe > the above ones, if the upstream branches were

Re: OpenJDK ports and 13-CURRENT

2020-10-10 Thread Yasuhiro KIMURA
From: Yasuhiro KIMURA Subject: Re: OpenJDK ports and 13-CURRENT Date: Sun, 11 Oct 2020 08:35:39 +0900 (JST) > From: Dimitry Andric > Subject: Re: OpenJDK ports and 13-CURRENT > Date: Sun, 11 Oct 2020 00:57:33 +0200 > >> Can you try the attached patch? I haven't yet looked at openjdk 13 and >> u

Re: OpenJDK ports and 13-CURRENT

2020-10-10 Thread Yasuhiro KIMURA
From: Yasuhiro KIMURA Subject: Re: OpenJDK ports and 13-CURRENT Date: Sun, 11 Oct 2020 08:35:39 +0900 (JST) >> Can you try the attached patch? I haven't yet looked at openjdk 13 and >> up, but I assume they will need at least the XSynchronize fix, and maybe >> the above ones, if the upstream bran

Re: FreeBSD Port: telegram-desktop-2.3.2 videocalls

2020-10-10 Thread Alex V. Petrov
I am not developer. I am user only. I don't have account on bugzilla. On 11.10.2020 05:30, Henry Hu wrote: > Okay, it seems like that there's a DCHECK related to threading. > However, if I disable the DCHECKs, video call seems to work. > It's not ideal, as typically these should not fail. But fo