Closed anarcat closed 5 years ago
@anarcat have you installed these dependencies?
sudo apt-get install libxext-dev libxtst-dev libxkbfile-dev g++ m4 automake libtool
i run Debian stable/jessie and it works for me, so i wonder what's different in our environments.
@anarcat ah yep, i can confirm the same error when i run the .AppImage
:
Error: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /tmp/.org.chromium.Chromium.o20JC0)
at Error (native)
at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:173:20)
at Object.Module._extensions..node (module.js:583:18)
at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:187:18)
at Module.load (module.js:473:32)
at tryModuleLoad (module.js:432:12)
at Function.Module._load (module.js:424:3)
at Module.require (module.js:483:17)
at require (internal/module.js:20:19)
at Object.<anonymous> (/tmp/.mount_w3fyvp/usr/bin/resources/app.asar/node_modules/keyboard-layout/lib/keyboard-layout.js:4:31)
normally i run Patchwork from the git repo and build locally.
@mmckegg what environment do you build these images in?
yes, i did.
@ahdinosaur OH NO! Not this again. Built on elementaryOS (which is ubuntu > debian).
Can you build it on your system and republish? I remember something similar to this a while back.
https://github.com/mmckegg/patchwork-next/issues/1#issuecomment-258320322
It turned out to be a problem with leveldown not depending on things correctly. I wonder if it's the same problem with keyboard-layout
?
nice find @mmckegg, was looking for that issue since i vaguely remembered this happening before. will do and see if that helps @anarcat. i'm also running a clean npm install
to see if anything breaks (edit: nothing broke).
oh also @anarcat, i notice
gyp ERR! node -v v0.10.29
gyp ERR! node-gyp -v v3.4.0
from https://github.com/ssbc/patchwork/issues/458#issuecomment-292363650, you might need to upgrade your node version, although i'm not sure what is the minimum required version, we're using the long-term stable version node@6.
hey @anarcat, can you try https://github.com/ssbc/patchwork/releases/download/v3.2.2/patchwork-3.2.2-linux-x86_64-1.AppImage?
or i also built the linux image for 3.3.0: https://github.com/ssbc/patchwork/releases/tag/v3.3.0.
On 2017-04-07 00:09:24, Mikey wrote:
i'm run Debian stable/jessie and it works for me, so i wonder what's different in our environments.
i may have some stuff from backports or stretch, but not much - it shouldn't make a difference, IMHO.
now, what i suspect is that you guys build with a more recent nodejs environment than me. ;) i have node.js 0.10.29~dfsg-2 and npm 1.4.21+ds-2. i understand this environment is moving fast and would totally understand if (say) i need to use the node.js backport (~4.7.2), but then that would need to be clarified in the docs!
I did try to upgrade node.js to the backports, but it seems something is broken on the debian side:
$ sudo LANG=C apt install -t jessie-backports nodejs
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
libssl-dev libssl1.0.0 libuv1
The following packages will be REMOVED:
node-gyp nodejs-dev npm
The following NEW packages will be installed:
libuv1
The following packages will be upgraded:
libssl-dev libssl1.0.0 nodejs
3 upgraded, 1 newly installed, 3 to remove and 544 not upgraded.
Need to get 6421 kB of archives.
After this operation, 9778 kB of additional disk space will be used.
Do you want to continue? [Y/n]
So I'm not sure where to go with this. Should I open a separate issue about the appimage stuff? That would seem like the biggest blocker...
a. -- Striving for social justice is the most valuable thing to do in life
@anarcat to clarify: are you saying the above linked AppImage builds didn't work for you?
and yes, i reckon we should test what versions of node this does work on and add it to the README.
ah yep, using node@0.10
failed for me too.
0.10
: FAILED0.12
: FAILED4
5
6
On 2017-04-07 08:06:35, Mikey wrote:
or i also built the linux image for 3.3.0: https://github.com/ssbc/patchwork/releases/tag/v3.3.0.
that works for me, thanks!
/usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21'
This means that the software needs a newer libstdc++.so.6 than what is provided by the system. If you compile on an older build system, it should work.
that works for me, thanks!
I'm taking this to mean that the problem is resolved, please reopen if that's not the case!
i get this trying to install patchwork here:
i tried compiling from scratch because the Appimage binary wouldn't work either:
a UI pops up that asks me if i want to register the app in my menus, i said no and it just gave me a blank window. maybe it's doing something funny, i don't know...