Pin Rust version for a specific server [duplicate] - rust

This question already has answers here:
Rust Linux version glibc not found - compile for different glibc / libc6 version
(2 answers)
How to generate statically linked executables?
(2 answers)
Closed 11 months ago.
I did a rust binary, which I compile in a ci with the rust docker image, tag rust:buster,
as my server was ubuntu 18.04
Lastly, I could not start the binary on the server anymore after the last compilation.
The error was :
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /home/xxx/.bin/ctprods)
Then I upgraded my server to ubuntu 21.10. The binary worked.
I want to fix the rust version in the ci.
Why did it stop working ?
How do I find the rust version for my server ?

Related

node-webcrypto-ossl, GLIBC_2.32 not found, Manjaro OS

When I try to run an application that uses node-webcrypto-ossl node module I get the error:
Error: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found.
Obviously node-webcrypto-ossl requires an older version of glibc.
The version of glibc installed on my machine is 2.33-5. I've tried downgrading my glibc but ended up with a broken system (fixed it already).
How do I resolve the issue?
Obviously node-webcrypto-ossl requires an older version of glibc.
No. GLIBC is backwards compatible: applications built against older version continue to run fine on newer GLIBC versions.
Your problem is the opposite: you have an application linked against GLIBC_2.32 trying to run against an older version of GLIBC.
The version of glibc installed on my machine is 2.33-5
The application is not using that version; it's using some other GLIBC.
The problem was that I was trying to run my app in docker ...
That's one way running against older than expected GLIBC could happen.

Latest NodeJS compatible with Windows 7 [duplicate]

This question already has answers here:
updating node.js in windows 7 64 bit
(5 answers)
Closed 1 year ago.
The community reviewed whether to reopen this question 8 months ago and left it closed:
Original close reason(s) were not resolved
I am trying to install NodeJS for windows 7. I tried installing the most recent NodeJS but it is not compatible with Windows 7. I was wondering if anyone knows what is the latest version of NodeJS you can install on Windows 7?
Thank you.
Update: Oct 2021, the latest versions working with below "trick" are:
Node v14.16.1 (or older but not below v14.5.0)
Node v15.8.0 (or older but not below v15.0.0)
Because Node updated from libuv v1.40 to v1.41,
and with that, causing Win7 errors:
ws2_32.dll does not have GetHostNameW function (or something alike).
The workaround Method (for versions mentioned above)
The v12.x branch seems to continue supporting Win7 (tested 2021 with Node v12.22.7).
But I needed 14.x version-branch and ended solving problem;
I just installed Node 14.15.0, like:
Go to Node-downloads
Download the Windows Binary (.zip) (either 32/64 bit)
Extract it in the directory where your node is installed and say yes to replace all files (remember that the zip comes with npm, which is in node_modules/npm directory; I didn't copy from the zip because I already updated npm before replacing the files)
Create an Environment variable called: NODE_SKIP_PLATFORM_CHECK and set it to 1
Ready to use Node in Windows 7 for now.
Latest node.js version that (officially) supports Windows 7 is 13.6.0.
https://nodejs.org/download/release/v13.6.0/
It seems that v13.14.0 is the last installer that works on Window 7
go here and select the package related to your version of windows 32 / 64 bits:
https://nodejs.org/dist/latest-v13.x/
I just install in Windows 7 x64 this version
https://nodejs.org/download/release/v13.14.0/

How to use different versions Nodejs for different react projects in Windows [duplicate]

This question already has answers here:
Install different versions of NodeJS
(7 answers)
Closed 4 years ago.
I'm currently using NodeJS 10 for my current react project but my 2nd react project is not compatible with node 10 and I need to use node 8 version but when I downloaded node 8 version and run msi file, it saying latest version is already installed on my machine and then end the installation.
I'm using windows.
How can I use two different node version on the same machine?
Use NVM (Node Version Manager) - Simple bash script to manage multiple active node.js versions.
Here you can find more details.
For Windows

Install glibc 2.15 in Red Hat 6.5 [duplicate]

This question already has answers here:
Multiple glibc libraries on a single host
(11 answers)
Closed 6 years ago.
I'm using openCV in my project. When I've tested in Red Hat instance, I have exception " /lib64/libc.so.6: version `GLIBC_2.15' not found".
So, how I can install glibc 2.15 in Red Hat?
I fond rpm(not 2.15(I hope new version can help me)), but I need some dependencies. Can I install glibc from some repo?
thx!
Can I install glibc from some repo?
Not likely: distributions usually don't ever update the major/minor version of glibc from the one they originally shipped with, because the likelihood of breaking applications is too great.
You may have to build glibc-2.15, or better current glibc-2.24 from source and install it into non-default location. See this answer.
If you are registered to satellite , Just run :
yum install glibc
this should take care of all .
If you are installing using rpms manually, you need dependent rpms as well.
Hope this helps.. Good luck.

Project ERROR: Unknown module(s) in QT: webkitwidgets [duplicate]

This question already has answers here:
Project ERROR: Unknown module(s) in QT: webkitwidgets
(6 answers)
Closed 8 years ago.
I'm trying to use MXE (with help from this tutorial), and I'm getting this error at the qmake && make step:
Project ERROR: Unknown module(s) in QT: webkitwidgets".
What does this mean and what can I do?
As per this similar answer, try installing the corresponding package. Assuming you have a Debian-based system, this is done by entering the following command in a console:
sudo apt-get install libqt5webkit5-dev
Unfortunately you're out of luck because recent versions of MXE do not build webkit. Apparently it has symbol conflict with the Qt script library, so the static build is impossible. Use the older MXE version, and don't forget to enable building the webkit in the src/qt.mk file.

Resources