RocketChat / RocketChat/Rocket.Chat
error adding symbols: file in wrong format
Open
Nobody has claimed this yet.
deployment
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
Hi! I use the manual installation method described here:
https://docs.rocket.chat/installation/manual-installation/ubuntu
For some reason the npm-rebuild.js fails with an error:
SOLINK_MODULE(target) Release/obj.target/sharp.node
/usr/bin/ld: ../vendor/lib/libvips-cpp.so: error adding symbols: file in wrong format
collect2: error: ld returned 1 exit status
make: *** [sharp.target.mk:199: Release/obj.target/sharp.node] Error 1
make: Leaving directory '/tmp/bundle/programs/server/npm/node_modules/sharp/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack at ChildProcess.emit (events.js:314:20)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:276:12)
gyp ERR! System Linux 5.4.0-1025-raspi
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /tmp/bundle/programs/server/npm/node_modules/sharp
gyp ERR! node -v v12.20.1
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
Steps to reproduce:
- Get a clean Linux Ubuntu environment on Raspberry Pi 4 (8GB)
- Follow the steps https://docs.rocket.chat/installation/manual-installation/ubuntu until
cd /tmp/bundle/programs/server && npm install
Expected behavior:
I can install
Actual behavior:
It won't install
Server Setup Information:
- Version of Rocket.Chat Server: Newest
- Operating System: Linux Ubunti Raspberry Pi version
- Deployment Method:
- Number of Running Instances: 0
- DB Replicaset Oplog: 0
- NodeJS Version: 12.20
- MongoDB Version: 4.4
Client Setup Information
- Desktop App or Browser Version:
- Operating System:
Additional context
Relevant logs:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Ubuntu manual-installation guide and the npm-rebuild.js step, then reproduce npm install on the reported Raspberry Pi 4 setup. Inspect the sharp build output and linked libvips error; done means the documented installation completes without the file-format linker failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, raspberry-pi, ubuntu
- Domain
- build-system, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100