Add /Developer/usr/bin to your path and try again.
Add /Developer/usr/bin to your path and try again.
Are you sure you installed Xcode and the other development tools as part of this fresh install? For example, are you sure you're not running Xcode from a different hard drive partition or something?
You should probably run the Mac OS X installer again and make sure to customize the install and select all the Xcode & developer tools.
When you installed the Apple Developer tools, did you also install the "Unix Development" package? From the Xcode 3.2.2 developer tools for Mac SDK 10.6 and iPhone SDK 3.2 README file:
Installation
The Xcode and iPhone SDK installer provides six options for configuring the installation from the “Customize...” button:
...
- UNIX Development. Command-line tools used for UNIX-based development. Its components are always placed in /usr - only one version installed at a time.
I believe that is what triggers putting the utilities into /usr/bin ...
Go to Preferences in Xcode, choose Downloads and install Command Line Tools.

macos - bash: make: command not found - Stack Overflow
macos - sudo: command not found - Ask Different
linux - bash - make command not found - Stack Overflow
macos - -bash: sudo: command not found Mac OS X (EC2 CLI prob?) - Stack Overflow
Make, among other things, is available through Apple's Command Line Tools. Install Command Line Tools through XCode by going to XCode->Preferences->Downloads
You can also download Command Line Tools without installing XCode from the Apple Developer site: https://developer.apple.com/opensource/
If you have XCode installed then @Wex's answer will get you going quickly, otherwise you don't have to install Xcode to get the command-line tools you seek.
Check this out: https://github.com/kennethreitz/osx-gcc-installer
You will want to install this one on Lion: https://github.com/downloads/kennethreitz/osx-gcc-installer/GCC-10.7-v2.pkg
Good luck!
Your PATH is hosed!
First check your .bash_profile file with:
/usr/bin/nano ~/.bash_profile
Prepend lines containing something like export PATH="/... " with a # to comment them out. Save the file with ctrlO and exit nano with ctrlX
Then check /etc/paths with: /bin/cat /etc/paths.
It should look like this:
/usr/local/bin
/usr/bin
/bin
/usr/sbin
/sbin
You can edit the file with /usr/bin/sudo /usr/bin/nano /etc/paths if required.
If everything is fine enter source ~/.bash_profile or close the Terminal window and open a new one.
Now sudo should work again. Then check all #export PATH=... lines in your .bash_profile for potential errors. You may add them to your question to get help here.
Magic Answer
export PATH="/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin"
As stated in the comments the right files to set up your $PATH variable are: ~/.profile or ~/.bash_profile
export PATH=/usr/bin:/usr/sbin:/bin:/usr/local/bin:/sbin:/opt/x11/bin:$PATH
In this way when you re-enter in the console your PATH will work fine.
You can add other directories to your $PATH as you like.
If you just copy and past that line in an active console you just set the PATH variable temporary, when you logout and login again you will loose your path, so add it in your ~/.bashrc file.
I'm not sure how you've managed to get into that state, though this article explains how you can set your path.
If it helps, the output from my echo $PATH is: -
/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin
By default sudo is not installed on Debian, but you can install it. First enable su-mode:
su -
Install sudo by running:
apt-get install sudo -y
After that you would need to play around with users and permissions. Give sudo right to your own user.
usermod -aG sudo yourusername
Make sure your sudoers file have sudo group added. Run:
visudo to modify sudoers file
and add following line into it (if it is missing):
# Allow members of group sudo to execute any command
%sudo ALL=(ALL:ALL) ALL
You need to relogin or reboot device completely for changes to take effect.
su and sudo are two different, but related commands. It is unusual for sudo not to be installed, but it may simply not be in your Path. Try /usr/bin/sudo command.
If indeed sudo is not available, you need as you surmised to use su, but it does not work in the same way as sudo. The simplest way to use it is to simply run:
su -
This will ask you for the root user's password, at which point you should probably apt install sudo, log out of the root shell, and then proceed as normal.
Mind that unlike sudo, which asks you for your password, su will ask you for root's password.