On 10 Oct 2020, at 21:49, Shawn Webb wrote:
>
> On Sat, Oct 10, 2020 at 09:45:58PM +0200, Dimitry Andric wrote:
...
>> The quick way to work around these errors is to set -fcommon in CFLAGS,
>> which will basically fudge around the actual issue. The better way is to
>> get rid of the duplicated
On 11 Oct 2020, at 08:57, Yasuhiro KIMURA wrote:
>
> 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
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 one
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 lo
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 bran
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
>>>
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
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
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?
>>
>>
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
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
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
12 matches
Mail list logo
