@wishmaster270 Okay, thanks for the explanation! I haven’t been able to read that anywhere in such clear words and I haven’t dealt with the past problems. Then I withdraw my recommendation because I lack the overview.
Read the statement by Michael Teeuw here.
Posts
-
RE: electron-rebuild problems with MagicMirror 2.22.0
-
RE: electron-rebuild problems with MagicMirror 2.22.0
@wishmaster270 OK, you’re welcome.
Since the thread is also for other developers: I recommend considering my approach, as I consider the other approach (installing to a higher-level directory) to be more error-prone. But it’s a creative workaround. -
RE: electron-rebuild problems with MagicMirror 2.22.0
Yes, but @electron/rebuild is the successor of electron-rebuild. And the “trick” in the postinstall script seems not necessary at all.
-
RE: electron-rebuild problems with MagicMirror 2.22.0
The problems on my machine are obviously of a different nature. I’ll investigate that later.
For the original issue it should be worth using
@electron/rebuildinstead ofmagicmirror-rebuildorelectron-rebuild. I tested it in a virtual machine and it works great. Here is my solution which is less invasive:
https://github.com/Tom-Hirschberger/MMM-GPIO-Notifications/pull/7What do you think?
-
RE: electron-rebuild problems with MagicMirror 2.22.0
For me it looks like this:
kristjan@debian:~/Infomonitor/MagicMirror/modules$ git clone https://github.com/sdetweil/MMM-Buttons.git Cloning into 'MMM-Buttons'... remote: Enumerating objects: 56, done. remote: Counting objects: 100% (4/4), done. remote: Compressing objects: 100% (4/4), done. remote: Total 56 (delta 0), reused 2 (delta 0), pack-reused 52 Receiving objects: 100% (56/56), 11.86 KiB | 1.69 MiB/s, done. Resolving deltas: 100% (25/25), done. kristjan@debian:~/Infomonitor/MagicMirror/modules$ cd MMM-Buttons/ kristjan@debian:~/Infomonitor/MagicMirror/modules/MMM-Buttons$ npm install npm ERR! code 1 npm ERR! path /home/kristjan/Infomonitor/MagicMirror/modules/MMM-Buttons/node_modules/epoll npm ERR! command failed npm ERR! command sh -c -- node-gyp rebuild npm ERR! make: Entering directory '/home/kristjan/Infomonitor/MagicMirror/modules/MMM-Buttons/node_modules/epoll/build' npm ERR! CXX(target) Release/obj.target/epoll/src/epoll.o npm ERR! SOLINK_MODULE(target) Release/obj.target/epoll.node npm ERR! make: Leaving directory '/home/kristjan/Infomonitor/MagicMirror/modules/MMM-Buttons/node_modules/epoll/build' npm ERR! gyp info it worked if it ends with ok npm ERR! gyp info using node-gyp@9.3.1 npm ERR! gyp info using node@16.18.0 | linux | x64 npm ERR! gyp info find Python using Python version 3.9.2 found at "/usr/bin/python3" npm ERR! gyp info spawn /usr/bin/python3 npm ERR! gyp info spawn args [ npm ERR! gyp info spawn args '/home/kristjan/Infomonitor/MagicMirror/node_modules/node-gyp/gyp/gyp_main.py', npm ERR! gyp info spawn args 'binding.gyp', npm ERR! gyp info spawn args '-f', npm ERR! gyp info spawn args 'make', npm ERR! gyp info spawn args '-I', npm ERR! gyp info spawn args '/home/kristjan/Infomonitor/MagicMirror/modules/MMM-Buttons/node_modules/epoll/build/config.gypi', npm ERR! gyp info spawn args '-I', npm ERR! gyp info spawn args '/home/kristjan/Infomonitor/MagicMirror/node_modules/node-gyp/addon.gypi', npm ERR! gyp info spawn args '-I', npm ERR! gyp info spawn args '/home/kristjan/.cache/node-gyp/16.18.0/include/node/common.gypi', npm ERR! gyp info spawn args '-Dlibrary=shared_library', npm ERR! gyp info spawn args '-Dvisibility=default', npm ERR! gyp info spawn args '-Dnode_root_dir=/home/kristjan/.cache/node-gyp/16.18.0', npm ERR! gyp info spawn args '-Dnode_gyp_dir=/home/kristjan/Infomonitor/MagicMirror/node_modules/node-gyp', npm ERR! gyp info spawn args '-Dnode_lib_file=/home/kristjan/.cache/node-gyp/16.18.0/<(target_arch)/node.lib', npm ERR! gyp info spawn args '-Dmodule_root_dir=/home/kristjan/Infomonitor/MagicMirror/modules/MMM-Buttons/node_modules/epoll', npm ERR! gyp info spawn args '-Dnode_engine=v8', npm ERR! gyp info spawn args '--depth=.', npm ERR! gyp info spawn args '--no-parallel', npm ERR! gyp info spawn args '--generator-output', npm ERR! gyp info spawn args 'build', npm ERR! gyp info spawn args '-Goutput_dir=.' npm ERR! gyp info spawn args ] npm ERR! gyp info spawn make npm ERR! gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ] npm ERR! /usr/bin/ld: /lib/x86_64-linux-gnu/libm.so.6: unknown type [0x13] section `.relr.dyn' npm ERR! /usr/bin/ld: skipping incompatible /lib/x86_64-linux-gnu/libm.so.6 when searching for /lib/x86_64-linux-gnu/libm.so.6 npm ERR! /usr/bin/ld: cannot find /lib/x86_64-linux-gnu/libm.so.6 npm ERR! /usr/bin/ld: /lib/x86_64-linux-gnu/libm.so.6: unknown type [0x13] section `.relr.dyn' npm ERR! /usr/bin/ld: skipping incompatible /lib/x86_64-linux-gnu/libm.so.6 when searching for /lib/x86_64-linux-gnu/libm.so.6 npm ERR! /usr/bin/ld: /lib/x86_64-linux-gnu/libmvec.so.1: unknown type [0x13] section `.relr.dyn' npm ERR! /usr/bin/ld: skipping incompatible /lib/x86_64-linux-gnu/libmvec.so.1 when searching for /lib/x86_64-linux-gnu/libmvec.so.1 npm ERR! /usr/bin/ld: cannot find /lib/x86_64-linux-gnu/libmvec.so.1 npm ERR! /usr/bin/ld: /lib/x86_64-linux-gnu/libmvec.so.1: unknown type [0x13] section `.relr.dyn' npm ERR! /usr/bin/ld: skipping incompatible /lib/x86_64-linux-gnu/libmvec.so.1 when searching for /lib/x86_64-linux-gnu/libmvec.so.1 npm ERR! collect2: error: ld returned 1 exit status npm ERR! make: *** [epoll.target.mk:145: Release/obj.target/epoll.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 (/home/kristjan/Infomonitor/MagicMirror/node_modules/node-gyp/lib/build.js:203:23) npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:513:28) npm ERR! gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:293:12) npm ERR! gyp ERR! System Linux 5.10.0-20-amd64 npm ERR! gyp ERR! command "/home/kristjan/.nvm/versions/node/v16.18.0/bin/node" "/home/kristjan/Infomonitor/MagicMirror/node_modules/.bin/node-gyp" "rebuild" npm ERR! gyp ERR! cwd /home/kristjan/Infomonitor/MagicMirror/modules/MMM-Buttons/node_modules/epoll npm ERR! gyp ERR! node -v v16.18.0 npm ERR! gyp ERR! node-gyp -v v9.3.1 npm ERR! gyp ERR! not ok npm ERR! A complete log of this run can be found in: npm ERR! /home/kristjan/.npm/_logs/2023-01-06T18_47_25_457Z-debug-0.log kristjan@debian:~/Infomonitor/MagicMirror/modules/MMM-Buttons$ uname -r 5.10.0-20-amd64 kristjan@debian:~/Infomonitor/MagicMirror/modules/MMM-Buttons$ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye -
RE: electron-rebuild problems with MagicMirror 2.22.0
To me this looks like a problem with the
onoffpackage. Because if I removeonofffrom thepackage.json,npm iworks.onoffalso comes with the dependencyepoll, which appears a lot in the error messages.npm i onoffandnpm i epollproduce similar error messages. I think that’s where the main problem is. -
RE: upgrade to new NPM version?
Since 6.14.12 there have been a lot of bug fixes, so an upgrade is recommended. And MM works fine with 8.19.2.
-
RE: ImOu Camera Rtspstream
Which module are you using and how did you configure it?
-
RE: Display More on Python Print Module
Out of curiosity: I can’t find any Python Print Module on the list of 3rd party modules. Which one is it exactly?
-
RE: display issue MMM-PublicTransportHafas
I now have no idea how we can solve this properly. Would it perhaps be a solution for you to integrate the module twice, with the two different IDs?
-
RE: MMM-Carousel - how to configure a module multiple times on the SAME page?
Thanks 🙂 I’ve created a Pull Request.
-
RE: MMM-KVV local Karlsruhe transport
The module uses the request package, which is not in the dependencies. Try
npm install requestin the module directory. -
RE: MMM-Carousel - how to configure a module multiple times on the SAME page?
@fantasmic78 I am glad that I could help.
It would be good to improve the documentation for such cases. Do you have a concrete suggestion how?
-
RE: MMM-Carousel - how to configure a module multiple times on the SAME page?
@fantasmic78 This should be possible with most modules. For example, I do this with MMM-JsonTable. The essential thing is that you use the same
carouselIdfor both module instances.
Try it that way and let me/us know if you can’t get it to work. -
RE: display issue MMM-PublicTransportHafas
@jo-0 Okay, I still think that there is something non-standard with the data from the transport company, but we can investigate this further. Can you try the configuration
ignoreRelatedStations: true,in combination with both stationIDs? -
RE: display issue MMM-PublicTransportHafas
That is interesting. Apparently, the transport company defined the station ‘Am Zwingerteich, Dresden’ as a related station of ‘Postplatz, Dresden’. Please try
stationID: "975242"- this is another ID for ‘Postplatz, Dresden’, which is not related to ‘Am Zwingerteich, Dresden’. -
RE: MMM-OlympicGames
@sirfm
localehas to be direcly under config not in the module config: https://github.com/fewieden/MMM-OlympicGames/blob/master/.github/global.png -
RE: MMM-OlympicGames
@mlhote In the meantime it works also with node-fetch v2 for me, so an upgrade seems not to be necessary.
One assumption is that this occurs when you restart the mirror several times. Then the API is often queried in a short time and therefore you are blocked.
-
RE: Updated Olympics module?
Even if this is an old question: MMM-OlympicGames has recently been updated.