#65691 closed defect (fixed)
filebrowser doesn't build on most systems
| Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | i0ntempest |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.7.2 |
| Keywords: | Cc: | ci42 | |
| Port: | filebrowser nodejs16 |
Change History (7)
comment:1 Changed 2 years ago by i0ntempest
comment:2 Changed 2 years ago by i0ntempest
Upstream issue: https://github.com/filebrowser/filebrowser/issues/2029
comment:3 follow-up: 4 Changed 2 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ci42 added |
|---|---|
| Port: | nodejs16 added |
On 7/7 it built successfully on all systems 10.7 and later.
Curious that on 7/20 and later it still built successfully on 10.7 and 10.8 (only).
nodejs16 was updated to 16.16.0 right after the last successful filebrowser builds. I downgraded nodejs16 to 16.15.1 and filebrowser builds fine. Sounds like a problem in nodejs16.
comment:4 Changed 2 years ago by i0ntempest
Replying to ryandesign:
On 7/7 it built successfully on all systems 10.7 and later.
Curious that on 7/20 and later it still built successfully on 10.7 and 10.8 (only).
Because 10.8 and 10.7 uses nodejs14 which uses openssl 1.1. Maybe it's caused by an update of openssl 3 that removed support for some legacy ciphers. I just tried building nodejs 16.16 with openssl 1.1, and filebrowser built fine with that. Check the PRs I've just opened, I'm not sure if we should add an openssl11 variant to nodejs16 or just peg it to 1.1 like in nodejs14 port.
comment:5 Changed 2 years ago by ryandesign (Ryan Carsten Schmidt)
The last update of openssl3 was on 7/5, before filebrowser last built successfully, so I don't see openssl3 as implicated in this issue.
comment:6 Changed 2 years ago by i0ntempest
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:7 Changed 2 years ago by i0ntempest
While this should now be fixed, Nodejs16 never supported linking OpenSSL 3 as stated here.
This
error:0308010C:digital envelope routines::unsupportedhas been happening after nodejs 16.16 update. Apprantly it's OpenSSL related. Upstream says cannot reproduce and our nodejs build might have problems.