title: Xcode 5.1 unable to find utility "make", not a developer tool or in PATH
body: <p>I am trying to follow <a href="http://www.giraffe-games.com/using-protobuf-protocol-buffers-on-iphone-ios/" rel="nofollow noreferrer">these directions</a> to install Google Protocol Buffers.  After creating the script, I try to run it with the following command:</p>
  
  <pre><code>$ ./build-proto-ios.sh
  </code></pre>
  
  <p>I receive the following output:</p>
  
  <pre><code>mkdir: ios-build: File exists
  Platform is iPhoneSimulator
  ./build-proto-ios.sh: line 40: ./configure: No such file or directory
  make: error: unable to find utility "make", not a developer tool or in PATH
  make: error: unable to find utility "make", not a developer tool or in PATH
  cp: src/.libs/libprotobuf-lite.a: No such file or directory
  Platform is iPhoneOS
  ./build-proto-ios.sh: line 40: ./configure: No such file or directory
  make: error: unable to find utility "make", not a developer tool or in PATH
  make: error: unable to find utility "make", not a developer tool or in PATH
  cp: src/.libs/libprotobuf-lite.a: No such file or directory
  Platform is iPhoneOS
  ./build-proto-ios.sh: line 40: ./configure: No such file or directory
  make: error: unable to find utility "make", not a developer tool or in PATH
  make: error: unable to find utility "make", not a developer tool or in PATH
  cp: src/.libs/libprotobuf-lite.a: No such file or directory
  make: error: unable to find utility "make", not a developer tool or in PATH
  fatal error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/lipo: can't open input file: ios-build/libprotobuf-lite-armv7.a (No such file or directory)
  </code></pre>
  
  <p>So, I looked for information on:</p>
  
  <blockquote>
    <p>unable to find utility "make", not a developer tool or in PATH</p>
  </blockquote>
  
  <p>I found <a href="https://stackoverflow.com/a/22799726/1735836">this information</a> for installing the Xcode command line tools, because I thought that might be the cause.  But even after installing the latest command line tools for OS X Mavericks, I'm still getting this error.</p>
  
  <p>Any ideas?</p>