[SOLVED] Having trouble locating file. Used FIND (file) ... should be simple
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Having trouble locating file. Used FIND (file) ... should be simple
I feel like a total doof ... Because this is a simple question, and right in the front of my brain the answer is floating ... But I just can't catch it.
I downloaded a gaming editor called BYOND. I unzipped, did CD to it's location, I ran Make, ./config, then make install ... Now I can't seem to locate the actual file.
First and foremost, I noticed that the order of the commands you listed are out of order; They should be as follows:
Code:
./configure
make
make check (optional)
make install (as root)
Now besides that, find searches recursively, but not backwards. If anything, you would have to search from root ( / ) to be able to search through all directories on your system. Lastly, when you do a "make install," you should have gotten output where the files have been installed to. You should be able to look in your output history in your shell and see where exactly the files were place.
What is the actual file you're looking for? The binary that was created when you ran make install to finish the compilation process? If so and if the compilation went OK then you should be able to locate the file with
Code:
which byond
if that is the name of the editor. Or did I misunderstand you?
What is the actual file you're looking for? The binary that was created when you ran make install to finish the compilation process? If so and if the compilation went OK then you should be able to locate the file with
Code:
which byond
if that is the name of the editor. Or did I misunderstand you?
Kind regards,
Eric
Yes I was looking for the binary, and it is an editor named BYOND ... You understood fine. I found the directory using corp's method, But when I do which byond I get nothing, it just goes back to
Glad you had it solved. The which command might fail when you don't have the path to the binary in your path statement, if you run it with sudo it might just work. Anyway, good job. Have fun with Linux.
Yes I was looking for the binary, and it is an editor named BYOND ... You understood fine. I found the directory using corp's method, But when I do which byond I get nothing, it just goes back to
Code:
me@here:$
To also add what Eric just said.... Could you give us the output of the following:
Code:
echo $PATH
The which command, like Eric said, looks in your path for the directories to look in. I'm just curious what all is in your path, that is all. And to think about it, also give the output when given with root privileges, that just might be the issue, like Eric said. Damn you Eric, you stole my thunder.
Distribution: Slackware (mainly) and then a lot of others...
Posts: 855
Rep:
Just adding to something that has been resolved . Did you kniw there was a 'locate <filename>' command? All you have to do is run 'updatedb' as root which will index all the files. Personally I prefer using locate to find.
Hope this helps.
Just adding to something that has been resolved . Did you kniw there was a 'locate <filename>' command? All you have to do is run 'updatedb' as root which will index all the files. Personally I prefer using locate to find.
Hope this helps.
Yes, but with find, you can search on the fly. With locate, it is very useful, which I use myself, but you need to run updatedb if not scheduled by cron.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.