#63774 closed defect (fixed)
nodejs16 built on Monterey causes Z_DATA_ERROR zlib checksum failure in npm
Reported by: | i0ntempest | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.7.1 |
Keywords: | monterey | Cc: | ci42, Tatsh (Andrew Udvare), phriedrich, knightcode (Dylan), stanft (Stephan Anft), amake (Aaron Madlon-Kay) |
Port: | nodejs16 |
Description
My port filebrowser requires a npm ci && npm run build
command, but nodejs16 built on Monterey fails to run this with:
:info:build npm verb Darwin 21.1.0 :info:build npm verb argv "/opt/local/bin/node" "/opt/local/bin/npm" "--verbose" "ci" :info:build npm verb node v16.13.0 :info:build npm verb npm v8.1.2 :info:build npm ERR! code Z_DATA_ERROR :info:build npm ERR! errno -3 :info:build npm ERR! zlib: incorrect data check :info:build npm verb exit -3
If I hack the MP build process to install the archive built for Big Sur, it runs fine. Complete log attached below.
nodejs17 gives a different SSL error but I didn't save the log.
Attachments (1)
Change History (12)
Changed 3 years ago by i0ntempest
comment:1 Changed 3 years ago by FaradayLight (Faraday Light)
comment:3 Changed 3 years ago by Tatsh (Andrew Udvare)
Cc: | Tatsh added |
---|
comment:4 Changed 3 years ago by phriedrich
Cc: | phriedrich added |
---|
comment:5 Changed 3 years ago by knightcode (Dylan)
Having the same issue on an x86_64 mac with Monterey 12.0.1. I tried downgrading to nodejs14 and got the same errors.
comment:6 Changed 3 years ago by knightcode (Dylan)
Cc: | knightcode added |
---|
comment:7 Changed 3 years ago by stanft (Stephan Anft)
Cc: | stanft added |
---|
comment:8 Changed 3 years ago by Tatsh (Andrew Udvare)
Linking against system zlib fixes the issue. https://github.com/macports/macports-ports/pull/12996
comment:9 Changed 3 years ago by amake (Aaron Madlon-Kay)
Cc: | amake added |
---|
comment:10 Changed 3 years ago by i0ntempest
Resolution: | → fixed |
---|---|
Status: | new → closed |
Fix confirmed, thanks
comment:11 Changed 3 years ago by Victor Oliveira <rhapsodyv@…>
Note: See
TracTickets for help on using
tickets.
This seems to be a possible cause of the problem: