Why can't it find it?

Question

Level 4

1,189 points

Why can't it find it?

I think this may speak for itself:
*SuperMac:~ dave$ which svn*
/usr/local/bin/svn
*SuperMac:~ dave$ svn*
*-bash: /usr/bin/svn: No such file or directory*
*SuperMac:~ dave$*

The shell obviously knows where svn is, so why won't it run without explicitly declaring the full path?

Thanks, Dave

4x Xeon, Mac OS X (10.5.7)

Posted on Aug 3, 2009 10:40 PM

Reply

Answer 1

jpimbert

Level 3

660 points

Aug 3, 2009 11:29 PM in response to David Hampson

Perhaps is there a logical, but broken, link between /usr/local/bin and /usr/bin ?

Reply

Answer 2

Jun T.

Level 4

2,185 points

Aug 3, 2009 11:50 PM in response to David Hampson

I guess you have an alias svn=/usr/bin/svn.
In bash, use "type" instead of "which":


type svn

Reply

Answer 3

David Hampson Author

Level 4

1,189 points

Aug 4, 2009 10:12 AM in response to David Hampson

type svn returns "/usr/local/bin/svn". Which is where the app is actually located.

I know a /should/ create an alias to where it really is, but that won't fix the problem of the shell looking in the wrong directory. (/usr/bin/svn)

--Dave

Reply

Answer 4

BobHarris

Level 9

53,309 points

Aug 4, 2009 4:30 PM in response to David Hampson

Try the following:


file /usr/local/bin/svn
ls -l /usr/local/bin/svn
alias svn

Because as has been suggested, it sounds like /usr/local/bin/svn is a symbolic link to /usr/bin/svn, only /usr/bin/svn doesn't exist.

And if not a symbolic link, then maybe /usr/local/bin/svn is a script which tries to invoke /usr/bin/svn.

Reply