Linux - Software This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
01-23-2004, 11:17 AM
|
#1
|
Member
Registered: Oct 2003
Location: Belgium
Distribution: Gentoo
Posts: 42
Rep:
|
compiling = no go
hi,
I'm having problems with compiling programs.
Each time i succeed at compiling any program and installing it, it fails to run. when i try to run it, bash just returns 'command not found', though i know i compiled and installed it right. I checked dependencies & the output of ./configure. I also tried installing it in an default directory, but still no go... :s
I use Suse 9 now, before i had redhat and never had such a problem. this is really annoying.
I would be really thankfull to anyone who gives me a hint on what is going on here.
greetz.
|
|
|
01-23-2004, 11:27 AM
|
#2
|
Member
Registered: Oct 2003
Location: Riverside, CA
Distribution: Slackware/RedHat
Posts: 79
Rep:
|
Hallo,
perhaps your search path is not defined wll enough. run the command 'whereis (programname)'
and then run the program using the complete path. if it works like that, then just find where your paths are stored and update them.
|
|
|
01-23-2004, 11:27 AM
|
#3
|
Senior Member
Registered: Sep 2003
Location: Sweden
Distribution: Debian
Posts: 3,032
Rep:
|
When you have compiled it, where does the actual executable that you would call to launch the program go? In most cases this would be /usr/local/bin, which should be in your path. If it's not, add it. To check if it's in your path, type echo $PATH and to add it to your path (if it's not there) use export PATH=$PATH:/usr/local/bin
If the program defaults to installing elsewhere you can often create a symbolic link to the executable in /usr/local/bin. Or you could simply add that directory to your $PATH too.
If it's a program you're not likely to use every day, just type the full location of the program to launch it: /usr/local/myapplication/myapp or whatever.
Håkan
|
|
|
All times are GMT -5. The time now is 01:45 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|