Missing "./configure" executables preventing successful install of tar files
Linux - EnterpriseThis forum is for all items relating to using Linux in the Enterprise.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Missing "./configure" executables preventing successful install of tar files
Hello All,
Thank you for your previous help. For the past two days, since installing Apache, PHP and a number of perl dependencies and packages for applications on my CentO 5.3 x64 VPS and CentOS 5.3 i386 dedicated server, I have been getting "-bash: ./configure: No such file or directory."
Everything is updated properly, including my kernels and all of the other packages on my servers. I'm not getting other install errors (except the typical Linux dependency resolving errors) when I use rpm or smart install.
I tried to find a recent error log (since I've only had the server three weeks), but the data contained in /var/log/yum.log don't provide data after January 21, 2009
Please let me know if you have any solutions-oriented ideas about how to solve this annoying problem. If you need more information, please let me know. Thank you.
Thank you for your previous help. For the past two days, since installing Apache, PHP and a number of perl dependencies and packages for applications on my CentO 5.3 x64 VPS and CentOS 5.3 i386 dedicated server, I have been getting "-bash: ./configure: No such file or directory."
Everything is updated properly, including my kernels and all of the other packages on my servers. I'm not getting other install errors (except the typical Linux dependency resolving errors) when I use rpm or smart install.
I tried to find a recent error log (since I've only had the server three weeks), but the data contained in /var/log/yum.log don't provide data after January 21, 2009
Please let me know if you have any solutions-oriented ideas about how to solve this annoying problem. If you need more information, please let me know. Thank you.
Sasha
YOu have been "getting" that message. How about telling us WHERE you're 'getting' it? What happens when it occurs? What's not working?
'./configure' is used, when the application has a configure script
in the top directory or somewhere else, e.g. src/ , else not.
( Sometimes configure is created by "other command" )
And if existing, ./configure is the second command to be run. The first command is : 'cd <directory-with-configure-script>'
.....
YOu have been "getting" that message. How about telling us WHERE you're 'getting' it? What happens when it occurs? What's not working?
Um, 'TBOne', maybe I don't understand your question or just think the answer is obvious so you'll have to excuse me if I get the sense that you're annoyed at my not having provided 'enough' information. Anyway, I "get" the message where one would typically "get" it--after I untar my package and type "./configure", the message occurs. Maybe you can tell me if there is another time it occurs because, clearly, I don't know.
Moreover, I "get" this message with any package that has to be built this way and have ever since I installed Apache 2, PHP and all of the perl packages I need for other apps on my server. Since that is the case, I did not bother to post any instances because they all look exactly the same.
I surmise that, since this only began happening after I installed the above-mentioned packages, the issue is either a conflict with some other installed package that is meant to configure packages but that are dependencies for some packages or the inability of the OS to locate the "./configure" executable associated with the particular package.
So, since I don't "get" why it's happening and am just trying to get some input from people here who want to be helpful without behaving like I slapped them because I didn't ask the question correctly.
April
P.S. For those who think my answer is over the top, I'm not the only Linux newbie who feels this way when we get responses with a tone like this one. I'm just one of those who doesn't feel my lack of knowledge about Linux means I'm just a plain moron, period, and, as such, should expect to be treated as such by those with far more superior knowledge about the OS. (See this article: Top 7 Reasons Why People Quit Linux)
I mean, don't get it twisted but I need to set the record straight. I appreciate responses--but I appreciate them more if they're helpful like those of most of the people who have been kind enough to post responses to my questions. (Read the next response from another senior member, knudfl, to know what I (and I'm sure most Linux users) mean. Expertise without snobbery or snarkiness. Love it!) I usually make a request in my posts that those whose answer will be like this one, and, therefore, unhelpful and a bit offensive in tone, not post responses to my questions. Yes, it limits the number of responses I get but it prevents debates and posting of useless information and responses (which I and others have to then read repeatedly, going back years, each time I research an issue I'm having and that's annoying!). It also precludes responses that discourage Linux newbs posting queries.
I get the most helpful answers and others find information they, too, can use when they come across the threads. Anyway, I've had it with these kinds of responses (which are often defended by others who say "so-and-so is one of our gurus so any information you get from them is like manna from Heaven" as harps play in the background while they type their obsequious post). I think it's time to speak up and I hope it's the last time I have to. (Well, actually, if my post isn't removed, I'll just link back to it. If it is, I'll post it all over the blogosphere.
Like many other Linux newbs who post here, I know far more about things that most people, never mind Linux experts, will ever know and am regarded as a knowledge resource (encyclopedia as some have said) in many areas. I write about some of those things and I don't treat those less knowledgeable than I in those areas or any other like idiots because they ask questions. I try to encourage them and let them know they CAN learn this or that.
The bottom line is I find this kind of behavior by a minority of Linux experts unnecessary and I would just like the Linux experts to either NOT to treat newbs like annoying butt sores OR NOT participate in forums like this where the clearly perceived by some as the great unwashed of the Windows world are coming to glean Linux knowledge. Just don't respond to the posts if you have little more to offer than sarcasm or snarkiness because just as you're free to speak, I'm free to respond.
Last edited by ajaygoeslinux; 05-11-2009 at 10:31 AM.
'./configure' is used, when the application has a configure script
in the top directory or somewhere else, e.g. src/ , else not.
( Sometimes configure is created by "other command" )
And if existing, ./configure is the second command to be run. The first command is : 'cd <directory-with-configure-script>'
.....
Thank you for your response because it is helpful and makes sense. From my research, I got the impression all of these applications had './configure' scripts and, although I usually read the installation instruction carefully before installing, I don't always see the reference to './configure'. I have tried "Makefile.PL" or "Build.PL" after reading someone's incomplete instructions on how to use the commands that I have to enter 'perl' first.
Here's a follow up question or two. How do I know which of these to use and how many can I try before I get the Windows BSOD equivalent (okay, I'm exaggerating but this is just as frustrating) on Linux--the fatal command, file lost forever message that requires me to start a square one?
Finally, I do switch directories but, clearly, not to the one where the './configure' script is located. Is there away to find out where that is without having to run "yum -c" between untarring and configuring?
Again, thank you for being as clear as I've seen instructions in a while. I wish others would remember that not everyone understands Linux when they post responses to these queries and would post their responses with that understanding.
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,511
Rep:
The most common ( and most easy ) way to do it :
Assume /home/"username"/tmp
cd tmp/
tar xvf <application>
cd <application>
Then you should be in the right directory ( most often.)
A good idea is to look for 'configure' in that directory,
using a file manager. No guaranty, 'configure' exists,
you may have to run run './autogen.sh' or something else
to create it. But please read the README, INSTALL, or
available documentation in the application or on the
internet for install instructions.
Lots of applications also have changed to 'cmake' or one
of the other build tools in the latest versions.
.....
If you see : Makefile.PL, run 'perl Makefile.PL' to
create the 'Makefile' .
CMakeLists.txt : run 'cmake ..' from a build directory.
setup.py : run 'python setup.py' etc.
.....
P.S. For those who think my answer is over the top, I'm not the only Linux newbie who feels this way when we get responses with a tone like this one. I'm just one of those who doesn't feel my lack of knowledge about Linux means I'm just a plain moron, period, and, as such, should expect to be treated as such by those with far more superior knowledge about the OS. (See this article: Top 7 Reasons Why People Quit Linux)
Um, 'TBOne', maybe I don't understand your question or just think the answer is obvious so you'll have to excuse me if I get the sense that you're annoyed at my not having provided 'enough' information. Anyway, I "get" the message where one would typically "get" it--after I untar my package and type "./configure", the message occurs. Maybe you can tell me if there is another time it occurs because, clearly, I don't know.
Great..you answered the question, which is why I asked it. In your original post, you didn't say when you got the message, or what you were doing to get it, just this:
Quote:
Thank you for your previous help. For the past two days, since installing Apache, PHP and a number of perl dependencies and packages for applications on my CentO 5.3 x64 VPS and CentOS 5.3 i386 dedicated server, I have been getting "-bash: ./configure: No such file or directory."
You didn't say "this happens when I untar package XXX, and type in ./configure". If you took it as being frustrated or whatever, that's fine. There was no "tone" in the message, just a question.
If you brought a car to your mechanic, and said "The warning light comes on", it stands to reason the mechanic would ask "WHICH warning light? When does it come on?". This is no different...if you ask for help, be sure to include all the details and describe the situation. It may be obvious to YOU, but it won't be to us.
Thank you for your response because it is helpful and makes sense. From my research, I got the impression all of these applications had './configure' scripts and, although I usually read the installation instruction carefully before installing, I don't always see the reference to './configure'. I have tried "Makefile.PL" or "Build.PL" after reading someone's incomplete instructions on how to use the commands that I have to enter 'perl' first.
Here's a follow up question or two. How do I know which of these to use and how many can I try before I get the Windows BSOD equivalent (okay, I'm exaggerating but this is just as frustrating) on Linux--the fatal command, file lost forever message that requires me to start a square one?
Finally, I do switch directories but, clearly, not to the one where the './configure' script is located. Is there away to find out where that is without having to run "yum -c" between untarring and configuring?
Again, thank you for being as clear as I've seen instructions in a while. I wish others would remember that not everyone understands Linux when they post responses to these queries and would post their responses with that understanding.
April
Which to use will depend on the package. I'd say well over 90% of Linux software will either include a readme or an install file (either in text or HTML that you can open with your web browser), that tells you the basics for installation. As knudfl said, there are lots of options.
Some basics:
Most software will create a directory of the same name. So if you download mypackage.tar.gz, then untar it, it'll *PROBABLY* create a "mypackage" directory. So, "cd mypackage", then you'll find the config scripts/software/instructions in there. For simplicity's sake, you may want to create a directory that you do nothing but download files to. A quick "ls" will tell you what's in there, and you'll easily be able to tell what new directories got created when you untar something. Also be aware that Linux is case sensitive...so "./Configure" is different from "./configure".
For Perl modules: Untar the file, and go into the directory it creates. Then "perl Makefile.PL", "make", "make test", then (as root) "make install".
For other software: Untar as above, go to directory. Then type in "./configure", "make", then (as root)"make install".
BUT you could also have to do an automake, edit a text file, or some other step(s). Be sure to always check the docs that come with it, and reference the web page if you get stuck.
And the BSOD doesn't apply, in the sense it does in Windows. A program may die, but it's very rare that you'll have to reboot....
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
