Because you didn’t tell many details, this can only be a guess.
1, ./configure is only used to generate GNU files in the Makefile automation tool, and sudo is not needed. make install is only needed for the last sudo.
2. Usually configure files have execution permission by default, but it is not completely guaranteed, so it is necessary to verify whether it has execution permission.
3, configureThe file will be generated, make sure you have write permissions in the current directory, otherwise you will not have enough permissions.
I was out a few days ago and didn’t have access to the Internet. Now I’ll give you some personal opinions and suggestions. If you find it useful, please adopt it. If you’re wrong, please point out any mistakes. If you think the answer is good, please give it a thumbs up~~
Brief description
First of all, I guess the questioner discovered this problem during the compilation and installation process, so I want to combine some instructions required for variant installation under Linux and their functions:
Compiling and installing software in Linux will use commands such as configure / make / make install . These are typical installation steps for programs generated using GNU's autoconf and automake.
./configure is used to detect the target characteristics of your installation platform. For example, it will detect whether you have CC or GCC. It does not require CC or GCC. It is a shell script.
make is used for compilation. It reads instructions from the Makefile and then compiles.
make install is used for installation. It also reads instructions from the Makefile and installs it to the specified location.
About configure
configure, this step is generally used to generate Makefile to prepare for the next step of compilation. You can control the installation by adding parameters after configure, such as:
./configure –prefix=/usr
The above means that if the software is installed under /usr, the executable files will be installed in /usr/bin (instead of the default /usr/local/bin), and the resource files will be installed in /usr/share ( instead of the default /usr/local/share).
At the same time, you can set the configuration files of some software by specifying the –sys-config= parameter. Some software can also add parameters such as –with, –enable, –without, –disable, etc. to control compilation. You can view detailed instructions and help by allowing ./configure –help.
Some common errors about configure
There are many common mistakes. Here is a blog that has collected a lot of them. You can go in and see if there are any that suit you. If so, then burn some incense~
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
~ chmod +x ./configure
~ ./configure
Remember to add execution permissions to the shell script on the new machine
Because you didn’t tell many details, this can only be a guess.
1,
./configureis only used to generateGNUfiles in theMakefileautomation tool, andsudois not needed.make installis only needed for the lastsudo.2. Usually
configurefiles have execution permission by default, but it is not completely guaranteed, so it is necessary to verify whether it has execution permission.3,
configureThe file will be generated, make sure you have write permissions in the current directory, otherwise you will not have enough permissions.You don’t have execution permissions? Check to see if you have permissions
You can only execute it with execution permission, otherwise you can only view and edit it.
But generally speaking, ready-made software packages will have execution permissions. What software are you installing?
Check if this file exists
Can your file be started directly (i.e. binary file)? If so, there is no need to configure
Thank you for the invitation~~
I was out a few days ago and didn’t have access to the Internet. Now I’ll give you some personal opinions and suggestions. If you find it useful, please adopt it. If you’re wrong, please point out any mistakes. If you think the answer is good, please give it a thumbs up~~
Brief description
First of all, I guess the questioner discovered this problem during the compilation and installation process, so I want to combine some instructions required for variant installation under Linux and their functions:
Compiling and installing software in Linux will use commands such as configure / make / make install
. These are typical installation steps for programs generated using GNU's autoconf and automake.
./configure is used to detect the target characteristics of your installation platform. For example, it will detect whether you have CC or GCC. It does not require CC or GCC. It is a shell script.
make is used for compilation. It reads instructions from the Makefile and then compiles.
make install is used for installation. It also reads instructions from the Makefile and installs it to the specified location.
About configure
configure, this step is generally used to generate Makefile to prepare for the next step of compilation. You can control the installation by adding parameters after configure, such as:
The above means that if the software is installed under /usr, the executable files will be installed in /usr/bin (instead of the default /usr/local/bin), and the resource files will be installed in /usr/share ( instead of the default /usr/local/share).
At the same time, you can set the configuration files of some software by specifying the –sys-config= parameter. Some software can also add parameters such as –with, –enable, –without, –disable, etc. to control compilation. You can view detailed instructions and help by allowing ./configure –help.
Some common errors about configure
There are many common mistakes. Here is a blog that has collected a lot of them. You can go in and see if there are any that suit you. If so, then burn some incense~
Website: http://freetstar.com/trouble-shooting-configure-make-make-install/