OK... as expected, it fails on macOS.
2 things I see: in the nss.patch file there is a line:
Only in misc/build/nss-3.39/nss/coreconf: Darwin.mk.rej
So I'm wondering if the patch file itself or maybe even the whole pull request
is borked.
Also, we need to force 'g++' on the macOS build to include '-std=c++11'
> On Oct 6, 2020, at 8:30 AM, Jim Jagielski <j...@jagunet.com> wrote:
>
> I am booting up the macOS VM for the 4.1.8-dev builds as we speak. Will
> update to head and pull in nss
>
>> On Oct 5, 2020, at 4:00 PM, Don Lewis <truck...@apache.org
>> <mailto:truck...@apache.org>> wrote:
>>
>> Any progress on nss?
>>
>> On 30 Sep, Jim Jagielski wrote:
>>> I'll see how the build on macOS goes, but likely won't be able to get to it
>>> until Monday.
>>>
>>>> On Sep 29, 2020, at 2:52 PM, Don Lewis <truck...@apache.org> wrote:
>>>>
>>>> On 29 Sep, Matthias Seidel wrote:
>>>>> Hi Don,
>>>>>
>>>>> Am 26.09.20 um 23:47 schrieb Don Lewis:
>>>>>> On 26 Sep, Matthias Seidel wrote:
>>>>>>> Hi all,
>>>>>>>
>>>>>>> Am 25.09.20 um 18:05 schrieb Matthias Seidel:
>>>>>>>> Am 25.09.20 um 14:01 schrieb Jim Jagielski:
>>>>>>>>> That looks quite a bit more straightforward :-)
>>>>>>>> Let's wait for Don's PR, this is only a minor update from Python 2.7.17
>>>>>>>> to 2.7.18.
>>>>>>> Merged now...
>>>>>>>
>>>>>>> Unless Don wants to add something for the Java detection I would think
>>>>>>> we are pretty close to a release candidate?
>>>>>> I've got another nss upgrade in the works as well as a small serf bug
>>>>>> fix.
>>>>>
>>>>> OK, if that can be done quick *and* safe?
>>>>
>>>> nss is somewhat risky. We've had problems with upgrading it in the
>>>> past, primarily with MacOS. It does fix a fairly important CVE, though
>>>> I don't know if it potentially affects our usage of nss. I just
>>>> submitted a pull request.
>>>>
>>>> Serf should be fairly quick. It's just a couple of patches
>>>> cherry-picked from upstream to fix a CVE.
>>>>
>>>> There are also a few new libxml2 CVEs, but not a new release of the
>>>> library. They can be fixed with some upstream cherry picks.
>>>>
>>>>> Otherwise I doubt that we have a release in the next 2 weeks... ;-)
>>>>>
>>>>> Regards,
>>>>>
>>>>> Matthias
>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>>>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>>>>
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>>> <mailto:dev-unsubscr...@openoffice.apache.org>
>>>> <mailto:dev-unsubscr...@openoffice.apache.org
>>>> <mailto:dev-unsubscr...@openoffice.apache.org>>
>>>> <mailto:dev-unsubscr...@openoffice.apache.org
>>>> <mailto:dev-unsubscr...@openoffice.apache.org>
>>>> <mailto:dev-unsubscr...@openoffice.apache.org
>>>> <mailto:dev-unsubscr...@openoffice.apache.org>>>
>>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>> <mailto:dev-h...@openoffice.apache.org>
>>>> <mailto:dev-h...@openoffice.apache.org
>>>> <mailto:dev-h...@openoffice.apache.org>>
>>>> <mailto:dev-h...@openoffice.apache.org
>>>> <mailto:dev-h...@openoffice.apache.org><mailto:dev-h...@openoffice.apache.org
>>>> <mailto:dev-h...@openoffice.apache.org>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> <mailto:dev-unsubscr...@openoffice.apache.org>
>> <mailto:dev-unsubscr...@openoffice.apache.org
>> <mailto:dev-unsubscr...@openoffice.apache.org>>
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>> <mailto:dev-h...@openoffice.apache.org>
>> <mailto:dev-h...@openoffice.apache.org
>> <mailto:dev-h...@openoffice.apache.org>>
