Re: GNU locate looking into a non-existant tree
site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 Dear Mo, I've got more simplifying to do now. Shalom, John B. Brown. [jbb@vcn.com] 358 High Street, Buffalo, Wyoming 82834 "Freedom is not worth having if it does not include the freedom to make mistakes" Mahatma Gandhi "If any question why we died, tell them, because our fathers lied." Rudyard Kipling "A man who does not know the truth is just an idiot but a man who knows the truth and calls it a lie is a crook." Bertolt Brecht "I wonder whether the world is being run by smart people who are putting us on or by imbeciles who really mean it." Mark Twain On 16-May-2010, at 00:55, John B Brown wrote: jbb@pinball3:~/gnu/build/findutils-4.4.2 (28): % hash locate jbb@pinball3:~/gnu/build/findutils-4.4.2 (29): % locate --version -bash: /usr/local/bin/locate: No such file or directory jbb@pinball3:~/gnu/build/findutils-4.4.2 (30): % hash /usr/bin/locate jbb@pinball3:~/gnu/build/findutils-4.4.2 (31): % locate --version -bash: /usr/local/bin/locate: No such file or directory In which case, you have an alias pointing at /usr/local/bin/locate. The error is quite definitely being produced by the shell itself. What does “type locate” say? Does a new terminal session work correctly? You’ve evidently got a customised profile, so I’d be looking there for the culprit. M. _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... Thank you for that. I found an alias left over from when I had MacPorts installed to make sure I used the locate I wanted, not something else. In simplifying I forgot all about that. It wasn't all an empty exercise; I compiled and installed Bash-4.1 because the hash apparently didn't work. Of course it did work but the alias torpedoed it, and my desires. On 5/15/10 5:59 PM, Mo McRoberts wrote: Apparently that is not the source of the error. This email sent to site_archiver@lists.apple.com
participants (1)
-
John B Brown