libfuse.so: error adding symbols: File in wrong format
-
@maverick
I don't have an oracle 8.8 build environment to check directly, but this error seems to imply node-gyp can't be found / started, or it is looking in the wrong place / there's a path difference between Oracle and Debian build environments.
code: 'ENOENT', syscall: 'spawn node-gyp', path: 'node-gyp', spawnargs: [ 'rebuild' ]Try 'npm install -g node-gyp' to make sure it is present? The same for node-gyp-build.
Do you also have the pkg-config rpm installed? And the native fuse libs rpm? The sagemathinc package will need these.
Cheers,
Mark
PS. I did run a 'yarn build' in my Debian VM and it built successfully after I gave it 3GB of RAM.
EDIT 24/Oct/2023: the -devel fuse libraries are needed too.
-
@Mark-C Hello Mark good morning and once more thanks for your feedback.
So, regarding installed libs, they are:
# dnf list installed | grep fuse fuse-common.aarch64 3.3.0-16.0.1.el8 @ol8_baseos_latest fuse-libs.aarch64 2.9.7-16.0.1.el8 @ol8_baseos_latest fuse3.aarch64 3.3.0-16.0.1.el8 @ol8_baseos_latest fuse3-libs.aarch64 3.3.0-16.0.1.el8 @ol8_baseos_latestthe node-gyp ... was installed before, as every
yarnran on thefix_fuse_dependancy_armbefore the pull ran successfully but worth the try:]# npm install -g node-gyp added 129 packages in 6s 17 packages are looking for funding run `npm fund` for details [root@xo-admin ~]# npm install -g node-gyp-build added 1 package in 465ms [root@xo-admin ~]# cd /opt/xen-orchestra [root@xo-admin xen-orchestra]# yarn yarn install v1.22.19 [1/5] Validating package.json... [2/5] Resolving packages... [3/5] Fetching packages... [4/5] Linking dependencies... warning "workspace-aggregator-81db5e50-50e8-4d08-ac0a-85a8882fd055 > @vates/node-vsphere-soap > soap@1.0.0" has incorrect peer dependency "axios@^0.27.2". warning Workspaces can only be enabled in private projects. [5/5] Building fresh packages... [14/19] ⠠ argon2 [13/19] ⠠ esbuild [12/19] ⠠ vue-echarts [4/19] ⠠ fuse-native error /opt/xen-orchestra/node_modules/fuse-native: Command failed. Exit code: 1 Command: node-gyp-build Arguments: Directory: /opt/xen-orchestra/node_modules/fuse-native Output: gyp info it worked if it ends with ok gyp info using node-gyp@9.4.0 gyp info using node@18.18.2 | linux | arm64 gyp info find Python using Python version 3.6.8 found at "/usr/bin/python3" gyp info spawn /usr/bin/python3 gyp info spawn args [ gyp info spawn args '/usr/local/lib/node_modules/node-gyp/gyp/gyp_main.py', gyp info spawn args 'binding.gyp', gyp info spawn args '-f', gyp info spawn args 'make', gyp info spawn args '-I', gyp info spawn args '/opt/xen-orchestra/fuse-native/build/config.gypi', gyp info spawn args '-I', gyp info spawn args '/usr/local/lib/node_modules/node-gyp/addon.gypi', gyp info spawn args '-I', gyp info spawn args '/root/.cache/node-gyp/18.18.2/include/node/common.gypi', gyp info spawn args '-Dlibrary=shared_library', gyp info spawn args '-Dvisibility=default', gyp info spawn args '-Dnode_root_dir=/root/.cache/node-gyp/18.18.2', gyp info spawn args '-Dnode_gyp_dir=/usr/local/lib/node_modules/node-gyp', gyp info spawn args '-Dnode_lib_file=/root/.cache/node-gyp/18.18.2/<(target_arch)/node.lib', gyp info spawn args '-Dmodule_root_dir=/opt/xen-orchestra/fuse-native', gyp info spawn args '-Dnode_engine=v8', gyp info spawn args '--depth=.', gyp info spawn args '--no-parallel', gyp info spawn args '--generator-output', gyp info spawn args 'build', gyp info spawn args '-Goutput_dir=.' gyp info spawn args ] Package fuse was not found in the pkg-config search path. Perhaps you should add the directory containing `fuse.pc' to the PKG_CONFIG_PATH environment variable Package 'fuse', required by 'virtual:world', not found Package fuse was not found in the pkg-config search path. Perhaps you should add the directory containing `fuse.pc' to the PKG_CONFIG_PATH environment variable Package 'fuse', required by 'virtual:world', not found gyp: Call to 'pkg-config --libs-only-L --libs-only-l fuse' returned exit status 1 while in binding.gyp. while trying to load binding.gyp gyp ERR! configure error gyp ERR! stack Error: `gyp` failed with exit code: 1 gyp ERR! stack at ChildProcess.onCpExit (/usr/local/lib/node_modules/node-gyp/lib/configure.js:325:16) gyp ERR! stack at ChildProcess.emit (node:events:517:28) gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:292:12) gyp ERR! System Linux 5.4.17-2136.324.5.3.el8uek.aarch64 gyp ERR! command "/usr/local/bin/node" "/usr/local/bin/node-gyp" "rebuild" gyp ERR! cwd /opt/xen-orchestra/fuse-native# find / -type f -iname fuse.pc # dnf whatprovides *fuse.pc Last metadata expiration check: 3:09:58 ago on Tue 24 Oct 2023 06:22:10 AM GMT. fuse-devel-2.9.7-12.0.1.el8.aarch64 : File System in Userspace (FUSE) v2 devel files Repo : ol8_baseos_latest Matched from: Other : *fuse.pc fuse-devel-2.9.7-12.0.2.el8.aarch64 : File System in Userspace (FUSE) v2 devel files Repo : ol8_baseos_latest Matched from: Other : *fuse.pc fuse-devel-2.9.7-12.0.3.el8.aarch64 : File System in Userspace (FUSE) v2 devel files Repo : ol8_baseos_latest Matched from: Other : *fuse.pc fuse-devel-2.9.7-12.0.4.el8.aarch64 : File System in Userspace (FUSE) v2 devel files Repo : ol8_baseos_latest Matched from: Other : *fuse.pc fuse-devel-2.9.7-15.0.2.el8.aarch64 : File System in Userspace (FUSE) v2 devel files Repo : ol8_baseos_latest Matched from: Other : *fuse.pc fuse-devel-2.9.7-16.0.1.el8.aarch64 : File System in Userspace (FUSE) v2 devel files Repo : ol8_baseos_latest Matched from: Other : *fuse.pc libconfuse-devel-3.3-7.el8.aarch64 : Development files for libconfuse Repo : epel Matched from: Other : *fuse.pc squashfuse-devel-0.1.104-1.el8.aarch64 : Development files for squashfuse Repo : epel Matched from: Other : *fuse.pc # dnf install -y fuse-devel Last metadata expiration check: 3:10:38 ago on Tue 24 Oct 2023 06:22:10 AM GMT. Dependencies resolved. ============================================================================================================================================================================================================================================ Package Architecture Version Repository Size ============================================================================================================================================================================================================================================ Installing: fuse-devel aarch64 2.9.7-16.0.1.el8 ol8_baseos_latest 44 k Transaction Summary ============================================================================================================================================================================================================================================ Install 1 Package Total download size: 44 k Installed size: 124 k Downloading Packages: fuse-devel-2.9.7-16.0.1.el8.aarch64.rpm 422 kB/s | 44 kB 00:00 -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Total 410 kB/s | 44 kB 00:00 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Installing : fuse-devel-2.9.7-16.0.1.el8.aarch64 1/1 Running scriptlet: fuse-devel-2.9.7-16.0.1.el8.aarch64 1/1 Verifying : fuse-devel-2.9.7-16.0.1.el8.aarch64 1/1 Installed: fuse-devel-2.9.7-16.0.1.el8.aarch64 Complete! [root@xo-admin xen-orchestra]# yarn yarn install v1.22.19 [1/5] Validating package.json... [2/5] Resolving packages... [3/5] Fetching packages... [4/5] Linking dependencies... warning "workspace-aggregator-fe799cd0-9fa4-4eaa-b335-8bcb3fdfd4a2 > @vates/node-vsphere-soap > soap@1.0.0" has incorrect peer dependency "axios@^0.27.2". warning Workspaces can only be enabled in private projects. [5/5] Building fresh packages... $ husky install husky - Git hooks installed Done in 50.84s.Going for the build now
-
@Mark-C kudus to you mate. Many thanks for your help, finally got it back.
]# yarn build yarn run v1.22.19 $ turbo run build --scope xo-server --scope xo-server-'*' --scope xo-web ╭────────────────────────────────────────────────────────────────────────╮ │ │ │ Update available v1.10.15 ≫ v1.10.16 │ │ Changelog: https://github.com/vercel/turbo/releases/tag/v1.10.16 │ │ Run "npx @turbo/codemod update" to update │ │ │ │ Follow @turborepo for updates: https://twitter.com/turborepo │ ╰────────────────────────────────────────────────────────────────────────╯ WARNING failed to contact turbod. Continuing in standalone mode: connection to turbo daemon process failed. To quickly resolve the issue, try running: - $ turbo daemon clean To debug further - please ensure the following: - the process identified by the pid in the file at /tmp/turbod/8288938151d980a6/turbod.pid is not running, and remove /tmp/turbod/8288938151d980a6/turbod.pid - check the logs at /root/.local/share/turborepo/logs/8288938151d980a6-xen-orchestra.log - the unix domain socket at /tmp/turbod/8288938151d980a6/turbod.sock has been removed You can also run without the daemon process by passing --no-daemon • Packages in scope: xo-server, xo-server-audit, xo-server-auth-github, xo-server-auth-google, xo-server-auth-ldap, xo-server-auth-oidc, xo-server-auth-saml, xo-server-backup-reports, xo-server-load-balancer, xo-server-netbox, xo-server-perf-alert, xo-server-sdn-controller, xo-server-test, xo-server-test-plugin, xo-server-transport-email, xo-server-transport-icinga2, xo-server-transport-nagios, xo-server-transport-slack, xo-server-transport-xmpp, xo-server-usage-report, xo-server-web-hooks, xo-web • Running build in 22 packages • Remote caching disabled Tasks: 26 successful, 26 total Cached: 0 cached, 26 total Time: 2m38.144s Done in 159.10s.
Super! Cheers mate!!
-
@maverick
Fab. Glad to see you got there and it builds on Oracle Linux ARM64 / aarch64 too! It'd be good to hear if you come across any functions that don't work on the aarch64 build.
I'm also sorry for the missing dependencies. I guess I had installed those early on in my attempts to get this compiled in August and missed them from the instructions. I'll go back and edit my post above to document them.
Cheers,
Mark
-
Wouldn't have made it without your help! Super.
So far everything seems to be working normally, except for my original issue on the other topic, posting there now.
If any more issues come up I'll post them here and reference on this topic. Many thanks!!