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.
I grabbed binutils from the gnu.org website, built it and installed it. I thought it was the latest version. However, the version that was installed was newer. I am using Cygwin with the bash shell. I delted the 'exe' files form the newly created directories (/usr/local/bin/) thinking that the PATH variable would re-direct the execution back to the main '/bin' path. When I execute the as.exe program I get the message 'bash: /usr/local/bin/as Nno such file or directory'. My quesion is how does bash know where the as.exe file used to be?
Distribution: approximately NixOS (http://nixos.org)
Posts: 1,900
Rep:
Oh. 'hash -r' works better. Really, set +h disables hashing at all (it means, shell doesn't try to remember where executables in PATH reside) and hash -r merely drops everything remembered, but allows to remember locations after it.
The /usr/local/bin would be the proper place for programs you download and build yourself. In the future, I would recommend not worrying about it and leaving it where the make install puts it.
The "set +h" turns off hashing. You may be able to run "set +h" followed by "set -h". The "set +h" step may dump a "hash cache". Try saying that three times fast!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.