Linux Lite Forums

Software - Support => Installing Software => Topic started by: Vera on July 09, 2018, 12:04:58 PM

Title: Software pgk compiled from source works but winds up in wrong direc. What to do?
Post by: Vera on July 09, 2018, 12:04:58 PM
UPDATE - not an issue anymore as explained below.
---

I just now installed the latest version of a piece of software via source code. No, I did not WANT to do it that way, I only did it because I needed the latest version, but Synaptic only had an older version that was missing critical features. This is for my LL 4.0 machine FYI.

I followed exact instructions from the package about downloading latest version and compiling, it gave me the commands to use. Everything seemed to go fine - there was a make command, a make check, and sudo make install. All looked good, the make check command showed everything as PASS. As you can probably tell, I have never done anything like this and am a total newbie to compiling. Anyway, since it all looked good and because it showed up properly on the man pages, I wanted to run it. Here is the problem:

When I try to run the command, I get an error from bash indicating that the software is not found in usr/bin.

I tried the catfish finder to see where it got compiled into. It went into usr/local/bin. If I run the software by typing in usr/local/bin/..., then it works.

This sounds well and good, but I am wanting to invoke it in a script, and it's clunky to have to type in usr/local/bin.... etc every time I want to use the command.

What is the best way to deal with this? Any ideas?

---
UPDATE: I don't know why or how, but now everything works as expected. I logged out and in between times, so maybe that's the reason for it working properly. Who knows what happened or why, but anyway, it's all working. Feel free to delete this entire question if needed - I couldn't figure out how to delete it.
Title: Re: Software pgk compiled from source works but winds up in wrong direc. What to do?
Post by: DeepThought on July 09, 2018, 01:43:01 PM
 /usr/local/bin and /usr/bin should both be part of your $PATH so it should have worked straight away, but sometimes a reboot or logout is required for new software to be recognised.

Glad you managed to sort it