Arch Linux User Repository

I am getting an error when building for aarch64. The extract from the log is

13 info lifecycle jitsi-meet-electron-utils@2.0.16~install: jitsi-meet-electron-utils@2.0.16
14 verbose lifecycle jitsi-meet-electron-utils@2.0.16~install: unsafe-perm in lifecycle true
15 verbose lifecycle jitsi-meet-electron-utils@2.0.16~install: PATH: /home/alarm/Downloads/jitsi-meet-desktop/src/.nvm/versions/node
/v14.17.1/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/alarm/Downloads/jitsi-meet-desktop/src/jitsi-meet-elect
ron-2.8.7/node_modules/jitsi-meet-electron-utils/node_modules/.bin:/home/alarm/Downloads/jitsi-meet-desktop/src/jitsi-meet-electron-
2.8.7/node_modules/.bin:/home/alarm/Downloads/jitsi-meet-desktop/src/jitsi-meet-electron-2.8.7/node_modules/.bin:/home/alarm/Downloa
ds/jitsi-meet-desktop/src/.nvm/versions/node/v14.17.1/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor
_perl:/usr/bin/core_perl
16 verbose lifecycle jitsi-meet-electron-utils@2.0.16~install: CWD: /home/alarm/Downloads/jitsi-meet-desktop/src/jitsi-meet-electron
-2.8.7/node_modules/jitsi-meet-electron-utils
17 silly lifecycle jitsi-meet-electron-utils@2.0.16~install: Args: [ '-c', 'prebuild-install || node-gyp rebuild' ]
18 silly lifecycle jitsi-meet-electron-utils@2.0.16~install: Returned: code: 1  signal: null
19 info lifecycle jitsi-meet-electron-utils@2.0.16~install: Failed to exec install script
20 verbose stack Error: jitsi-meet-electron-utils@2.0.16 install: `prebuild-install || node-gyp rebuild`
20 verbose stack Exit status 1

Any ideas?

A quick note on the most recent update:

I've reverted the patch (https://github.com/jitsi/jitsi-meet-electron/commit/0e0483cbc52a9cad1fef51ed5abb846bd6445b11) for pipewire screensharing support, as that change caused jitsi-meet-desktop to hang / not launch on swaywm with the following flags for native wayland support in my ~/.config/electron12-flags.conf:

--enable-features=UseOzonePlatform
--ozone-platform=wayland

The flag (--enable-features=WebRTCPipeWireCapturer) can be easily applied, if desired, by putting it in this very file (~/.config/electron12-flags.conf) individually, which I think is a saner approach to using it anyway.

It might work fine on other setups, but at least on my system (with sway-git and wlroots-git), it doesn't work.

@je-vv:

Those issues should be fixed now, hopefully (those of @jsamr as well, I think :).

oh well, with last change (2.8.6-2) building jitsi-meet-desktop leaves ~/.npm dirty... I guess the build stage is not doing anything to change the cache directory as it was done on on the prepare stage. Perhaps adding the env var setting:

export npm_config_cache="${srcdir}/npm_cache"

also to the build stage? Or perhaps it's being set too late on the prepare stage? I can't tell, but maybe using:

unset npm_config_prefix
export npm_config_cache="${srcdir}/npm_cache"

at the beginning of prepare() might solve things, and if not enough, then at the beginning of both, prepare() and build()

@jsamr the npm_config_prefix environment variable is (to my knowledge) not there "by default" (ie. it has to be set somewhere in your environment).

Still, for the sake of getting this package built it should be sufficient to follow the recommendation in the error message: add unset npm_config_prefix in the PKGBUILD, so the environment variable will be temporarily unset in during the build process so nvm can do its thing. I'd add it right after the prepare() { line, to give it a try.

Alternatively, you could always resort to https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot :)

Can't make this package with nodejs installed.

v14.17.0 is already installed.
nvm is not compatible with the "npm_config_prefix" environment variable: currently set to "/home/jsamr/.node_modules"
Run `unset npm_config_prefix` to unset it.
Creating default alias: default -> 14 (-> v14.17.0)
nvm is not compatible with the "npm_config_prefix" environment variable: currently set to "/home/jsamr/.node_modules"
Run `unset npm_config_prefix` to unset it.
==> ERROR: A failure occurred in prepare().
    Aborting...
error making: jitsi-meet-desktop

@lsf, btw, nodejs-webpack-cli provides nodejs-webpack it seems, so if looking into it, perhaps nodejs-webpack-cli becomes a better option, :)

I'm not sure if I did something wrong but this kept failing to compile after installing nvm and nvm-git and the command works for my user.

I edited the PKGBUILD to remove the line, nvm unalias default using and ran the command after compiling.

edit: Clarified what I deleted

That might be an issue considering we're using nvm – but it might be a good idea to try. I'll give it a spin and see how it goes :)

why aren't nodejs-webpack and/or nodejs-webpack-cli packages optional build time dependencies to avoid downloading them as well? Aren't they needed any longer? They are opt deps for jitsi-meet-electron. I think if system ones could be used, that's way better than downloading them every time, :) Not sure if both needed though, perhaps, just the *-cli package?

@lsf, it's fine, it's just one line, and perhaps the right one, :) It gets generated at $HOME... Thanks !