Fix seamonkey build breakage from nss-3.65.

[ken@…]

AFAICS, for the next week no mozilla releases or betas will require nss-3.65 (after ff90 is in beta, that might change).

In the meantime, Jean-Marc on blfs-dev has confirmed the seamonkey build breakage and identified that reverting to nss-3.64 allowed seamonkey to build. I've now confirmed that, so I suggest we should temporarily revert to nss-3.64.

Edit: changed summary, based on upstream feedback.

[Douglas R. Reno]

Can you try replacing CLEANUP with Cleanup? I'm looking at the version in ESR78 (​https://hg.mozilla.org/releases/mozilla-esr78/file/tip/dom/indexedDB/IDBTransaction.h), and I see Cleanup instead of CLEANUP.

[ken@…]

Bug raised against seamonkey build system (might be wrong component, or they might say it is an nss bug) ​https://bugzilla.mozilla.org/show_bug.cgi?id=1712625

[ken@…]

Replying to Douglas R. Reno:

Can you try replacing CLEANUP with Cleanup? I'm looking at the version in ESR78 (​https://hg.mozilla.org/releases/mozilla-esr78/file/tip/dom/indexedDB/IDBTransaction.h), and I see Cleanup instead of CLEANUP.

I looked at current firefox when I first hit this, and the file in seamonkey is very different (much older). I think Bruce is going to try using the shipped nss. Or perhaps upstream might make a comment.

[Bruce Dubbs]

I was able to build SM by disabling system nss. I think that is a better solution than reverting nss.

[ken@…]

Upstream agrees, except maybe also disable system nspr. But if it works with system nspr then that should be good enough.

Seamonkey will only gain support for later nss and nspr versions after (firefox) ESR 91 appears, currently it is targeted at the versions in firefox-78esr (nss-3.53.1 and nspr-4.25 in ff78.10.1).

I assume the build will be bigger and slower. Will measure it when I get that far on my new build.