Error on a Rasperry Pi Jessie OS (ARM) #30

Activity

1. audstanley commented on Jul 8, 2021

   

   audstanley

   on Jul 8, 2021

   Last edited by audstanley

   Owner

   More actions

   Thank you for posting - and yes, glibc is a source of pain with GoLang. Same kind of issues when compiling binaries in GoLang for Alpine Linux.
2. audstanley

   closed this as completedon Jul 8, 2021
3. audstanley

   pinned this issue on Jul 8, 2021
4. audstanley

   reopened this on Jul 8, 2021
5. audstanley commented on Jul 8, 2021

   

   audstanley

   on Jul 8, 2021

   Last edited by audstanley

   Owner

   More actions

   Wait - I just realized that this was a NodeJs error, and not an error with the installer? Interesting. I imagine that installing Node Version 8 might work on Jessy? I'm not sure what the cut off is if you're going to use an older distro.

   Let me know what you find - I might have consider building in a distro check for older versions of Raspbian OS... or just state in the README.md that Jessy is no longer supported.
6. SuganNaickerf commented on Jul 8, 2021

   

   SuganNaickerf

   on Jul 8, 2021

   Author

   More actions

   Wait - I just realized that this was a NodeJs error, and not an error with the installer? Interesting. I imagine that installing Node Version 8 might work on Jessy? I'm not sure what the cut off is if you're going to use an older distro.

   Let me know what you find - I might have consider building in a distro check for older versions of Raspbian OS... or just state in the README.md that Jessy is no longer supported.

   Thanks for the feedback. I needed minimum NodeJS version 10 in order for another app to work. I tried upgrading Jessie, but that itself did not solve my issues. Finally had to use a 'clean' image with the latest Buster (rather than upgrading).
7. audstanley commented on Jul 8, 2021

   

   audstanley

   on Jul 8, 2021

   Owner

   More actions

   Awesome! and thank you... I think that I'll just state that Jessy and Stretch aren't supported - It seems that GLIBC has changed the game for a LOT of Distros - I think we can thank containers for the code change in the dependency. I'll try a fresh version of Buster and see if I can run a really old version of NodeJs [v4] with the installer. I'm guessing that newer version GLIBC is backwards compatible, but I'm not completely sure... I'm not even sure people are running that old of a Node version anyway... but it's worth noting either way. So yeah, I'll likely just stick an update in the readme. 🙌
8. audstanley commented on Sep 28, 2021

   

   audstanley

   on Sep 28, 2021

   Last edited by audstanley

   Owner

   More actions

   I think detecting the OS Jessy/Stretch and than getting/building GLIBC may not be the answer since this is a Node dependency. I'm not sure what to do since the older OS might be dependent on older GLIBC for web based actions. I'm going to just keep the issue open so that people running an old pi os are aware that this is a problem. Maybe compiling the new GLIBC and changing it on the older OS would work just fine, though I just think it's outside of the scope of this project.
9. audstanley commented on Sep 28, 2021

   

   audstanley

   on Sep 28, 2021

   Last edited by audstanley

   Owner

   More actions

   weird, the installer/node works fine on my x64 running ubuntu, and:

   $ ldd --version
   ldd (Ubuntu GLIBC 2.34-0ubuntu2) 2.34
   Copyright (C) 2021 Free Software Foundation, Inc.
   This is free software; see the source for copying conditions.  There is NO
   warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
   Written by Roland McGrath and Ulrich Drepper.

   maybe the GLIBCXX_3.4.21 dependency is architecture dependent when it comes to node?
   Note: I'm on ubuntu 21.10 also (super bleeding edge) 🙂 .
10. audstanley commented on Nov 2, 2021

    

    audstanley

    on Nov 2, 2021

    Owner

    More actions

    I think I was finally able to solve this problem on issue #31 - So I'm going to close this, and if the problem comes up again - I'll reopen - The problem was that I was compiling and cross compiling on a machine where GLIBC was too new, and newer version of GLIBC seem to work fine when using the compiled binaries utilizing GLIBC version 3.31
11. audstanley

    closed this as completedon Nov 2, 2021
12. SuganNaickerf commented on Nov 3, 2021

    

    SuganNaickerf

    on Nov 3, 2021 via email

    Author

    More actions

    Hi, Thank you for the feedback. Regards, Sugan Naicker Dev-X Digital Solutions (Pty) LTD Website : www.dev-x.co.za Email : ***@***.***

    …

    ---------------------------------------- From: Richard Stanley ***@***.***> Sent: 11/2/21 11:49 PM To: audstanley/NodeJs-Raspberry-Pi ***@***.***> Cc: SuganNaickerf ***@***.***>, Author ***@***.***> Subject: Re: [audstanley/NodeJs-Raspberry-Pi] Error on a Rasperry Pi Jessie OS (ARM) (#30) I think I was finally able to solve this problem on issue #31 - So I'm going to close this, and if the problem comes up again - I'll reopen - The problem was that I was compiling and cross compiling on a machine where GLIBC was too new, and newer version of GLIBC seem to work fine when using the compiled binaries utilizing GLIBC version 3.31 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.