Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

10.5: A solution for PackageMaker failing in 10.5 System 10.5
If you've used the PackageMaker command line tool in 10.4, and tried to run the same command in 10.5, you may experience a failure with the error:

*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'launch path not accessible'

This is because otool is in /Developer/usr/bin and not in /usr/bin where PackageMaker is expecting it. Simply symlink to otool by typing:
ln -s /Developer/usr/bin/otool /usr/bin/otool
[robg adds: Over on the queue site, a comment notes that the only time this will happen is if the user unchecks the UNIX Development Support option in the Xcode installer. This feature, which is enabled by default, is described by Apple in this way: "Optional content to allow command-line development from the boot volume. Installs a duplicate of the GCC compiler and command line tools included with the core Xcode developer tools package into the boot volume. It also installs header files, libraries, and other resources for developing software using Mac OS X into the boot volume. This package is provided for compatibility with shell scripts and makefiles that require access to the developer tools in specific system locations. This content is not relocatable and will only be installed onto the boot volume." Thanks, fds!]
  • Currently 3.33 / 5
  You rated: 3 / 5 (6 votes cast)

10.5: A solution for PackageMaker failing in 10.5 | 0 comments | Create New Account
Click here to return to the '10.5: A solution for PackageMaker failing in 10.5' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.