1 Reply Latest reply: Sep 6, 2009 10:43 AM by pantopic
pantopic Level 1 Level 1
I was working through the Applescript Action tutorial and I found that when I try to compile the action that the following error appears:

Running custom shell script:
  x line 2: /usr/bin/amlint: No such file or directory.

When I installed Snow Leopard, the placing of /Developer/usr/bin into $PATH somehow got broken. I entered it myself into /etc/profile and ~/.MacOSX/environment.plist. Xcode seems not to have any trouble finding anything else in that directory now and amlint produces a usage message when I call it from the command line without the full path and the man page is available. Is there some way to force XCode to find this program? Without it, you can't produce automator actions; from the name, it is the static checker for automator actions and is called from the build script.

iMac 2.4 Ghz Core 2 Duo, Mac OS X (10.6)
  • pantopic Level 1 Level 1
    I solved the problem (in the sense that XCode can now find amlint), by linking /Developer/usr/bin/amlint to /usr/bin. I suppose that this is what I need to do with all the executables in /Developer/usr/bin/ to make sure this doesn't happen again (rather than just adding /Developer/usr/bin/ to $PATH).