Thanks for the info, for now --openssl-legacy-provider fixed the build for filebrowser. I have a PR open for nodejs16 adding an openssl11 variant, but I’ll probably change it to just ping to openssl11 instead.
Zhenfu > On Aug 19, 2022, at 08:41, David Gilman <davidgilm...@gmail.com> wrote: > > When I did some sleuthing on this topic, which resulted in > https://trac.macports.org/ticket/65515 , this was my finding: > > - node before 17 doesn't really support openssl 3, resulting in the > error you and I are seeing. > https://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V17.md#2021-10-19-version-1700-current-bethgriggs > - node 16.17 added --openssl-legacy-provider, which allows for openssl > 3 to work on node 16. However, this is an ugly breaking change: > everyone needs to tweak their CLIs or export this through NODE_OPTIONS > envvar. > - for compatibility, node 16 and before should just build against > openssl 1.1 by default. This is the combination that's being used by > pretty much everyone out there. > > On Thu, Aug 18, 2022 at 10:32 PM Zhenfu Shi <i0ntemp...@macports.org> wrote: >> >> Hi all, >> Can someone please help me getting this error figured out? This error has >> been occurring since Nodejs 16.16 update and borked the build of my >> filebrowser port on all systems. Apparently it’s OpenSSL related, but all >> the workarounds I found failed in a way or another. Upstream said they could >> not reproduce this and our nodejs might have issues. >> >> Build log: >> https://build.macports.org/builders/ports-12_x86_64-builder/builds/39078/steps/install-port/logs/stdio >> Ticket: https://trac.macports.org/ticket/65691 >> Upstream issue: https://github.com/filebrowser/filebrowser/issues/2029 >> >> Thanks, >> Zhenfu > > > > -- > David Gilman > :DG<
