Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Mmm are you sure that's the correct way of doing that process? When compiling programs the first step is to read documentation: at least README or INSTALL files that usually come along the project. There it's told how you should compile the code. The usual way is ./configure, which does the pre-compilation configuration, and if it succeeds (note: any errors should be taken seriously and fixed, and after configure is re-run successfully, continue -- and only then), 'make' which actually compiles the code and then as root 'make install' which installs the compiled files (copies them in their places in the system). That's the basic way, but then again many projects provide a single file that's run to do the whole process (like install.sh for example). Your way may be perfectly appropriate, but please do make it certain.
Most of the time I compile programs and face errors that sound like those in your post it's because the configure part didn't go trough successfully, or because I need to pass extra parameters to configure to guide it do the configuration process (and then guide the compilation process) correctly. I'm pretty sure the creator of that code tells you how to do stuff like this (i.e. how to configure and install the source the right way) either in a website or in the documentation provided along the code. Usually the worst way of starting to compile something is just ramming at it..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.