It is recommended to use the file command to check whether the file is 32-bit or 64-bit. Generally, this problem will occur if a 32-bit program is executed on a 64-bit system. It is possible that the program you compile is 32-bit.
I don’t have Ubuntu around me, I found unar’s replacement unar on centos
[root@web ~]# yum info unar
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
Available Packages
Name : unar
Arch : x86_64
Version : 1.10.1
Release : 1.el7
Size : 1.9 M
Repo : epel-home
Summary : Multi-format extractor
URL : http://unarchiver.c3.cx/commandline
License : LGPLv2+
Description : The command-line utilities lsar and unar are capable of listing and extracting
: files respectively in several formats including RARv3. unar can serve as a free
: and open source replacement of unrar.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
It is recommended to use the file command to check whether the file is 32-bit or 64-bit. Generally, this problem will occur if a 32-bit program is executed on a 64-bit system. It is possible that the program you compile is 32-bit.
unrar is not necessarily in the /usr/local/bin directory
You can use the find command to confirm that unrar is in that directory
If found, add the directory to the PATH variable
/usr/local/bin is unrar*
Can you post your compilation parameters?
I don’t have Ubuntu around me, I found unar’s replacement unar on centos