RocketChat / RocketChat/Rocket.Chat

Error deploying on Debian / latest `/usr/bin/ld: cannot find -lz: No such file or directory`

Open
#30,856 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

Error at compilation time while trying to deploy on debian.

Steps to reproduce:

Follow https://docs.rocket.chat/deploy/deploy-rocket.chat/additional-deployment-methods/deploy-on-debian

Expected behavior:

No error.

Actual behavior:

Error at step (cd /tmp/bundle/programs/server; npm i)


npm ERR! <command-line>: note: this is the location of the previous definition
npm ERR! ../src/module/lib_handle.cc: In member function 'v8::Local<v8::Value> ivm::LibHandle::PrivateSymbol(v8::MaybeLocal<v8::String>)':
npm ERR! ../src/module/lib_handle.cc:58:17: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
npm ERR!    58 |         return *reinterpret_cast<Local<Value>*>(&symbol);
npm ERR!       |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! ../src/module/lib_handle.cc:58:17: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
npm ERR! /usr/bin/ld: cannot find -lz: No such file or directory
npm ERR! /usr/bin/ld: cannot find -lbrotlidec: No such file or directory
npm ERR! /usr/bin/ld: cannot find -lbrotlienc: No such file or directory
npm ERR! /usr/bin/ld: cannot find -lcares: No such file or directory
npm ERR! /usr/bin/ld: cannot find -lnghttp2: No such file or directory
npm ERR! /usr/bin/ld: cannot find -licui18n: No such file or directory
npm ERR! /usr/bin/ld: cannot find -licuuc: No such file or directory
npm ERR! /usr/bin/ld: cannot find -licudata: No such file or directory
npm ERR! collect2: error: ld returned 1 exit status
npm ERR! make: *** [isolated_vm.target.mk:232: Release/obj.target/isolated_vm.node] Error 1
npm ERR! gyp ERR! build error 
npm ERR! gyp ERR! stack Error: `make` failed with exit code: 2
npm ERR! gyp ERR! stack     at ChildProcess.onExit (/tmp/bundle/programs/server/node_modules/node-gyp/lib/build.js:194:23)
npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:513:28)
npm ERR! gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:291:12)
npm ERR! gyp ERR! System Linux 6.1.0-13-amd64
npm ERR! gyp ERR! command "/usr/bin/node" "/tmp/bundle/programs/server/node_modules/.bin/node-gyp" "rebuild" "--release" "-j" "4"
npm ERR! gyp ERR! cwd /tmp/bundle/programs/server/npm/node_modules/isolated-vm
npm ERR! gyp ERR! node -v v18.13.0
npm ERR! gyp ERR! node-gyp -v v8.0.0

I had to install each libs manually ; is something missing ? Or I have missed a step ?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the deploy-on-Debian guide linked in the issue and reproduce the (cd /tmp/bundle/programs/server; npm i) step on Debian. Check which prerequisites are missing for the isolated-vm build and update the deployment instructions so a fresh deployment completes without the linker errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
debian, linux, node.js
Domain
build-system, devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.