• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL

Part: V Advanced Command-Line Concepts > Troubleshooting Software Installs, and...

Chapter 17. Troubleshooting Software Installs, and Compiling and Debugging Manually

In This Chapter

Sometimes, when you try to compile and install a program, it won't work as easily as the examples we've shown in the previous chapter. Sometimes it's a matter of the program not being tweaked to run properly on OS X. Sometimes the program is just poorly written. Most often, however, it's because the vast majority of software written for Unix is in a constant state of revision, and minor bugs are introduced, and squashed again, on a regular basis. If you're in no hurry to use the software, don't worry that it doesn't compile. As long as you've paid attention to this suggestion: Never compile or install software as a user with a privileged account. The attempt to compile and run it has done nothing more than occupy some disk space and cause a little frustration. Write to the program's author, let him or her know that something's not right, and it will probably be fixed in a reasonable amount of time.

If you're in a hurry, or are either inquisitive or stubborn, there are some things that you can try to get the software working. A few of these involve updating certain parameters in your environment, one involves rolling up your sleeves and digging around in the program's guts. If the latter is something you've never imagined doing, don't worry—it's your choice! Just remember that as long as you're working in a nonprivileged account, you can't really do much damage—the software is already broken, you can't hurt the system. The worst that will happen is you don't improve anything.

This chapter will lay out a few common things to check when an install doesn't seem to work, and take you through an example of what is necessary to fix one particularly troublesome install. Because every problem install will be different, we can't give you an exhaustive list of things to look for. Instead, we hope the tour of a problematic install and the example of using the GNU debugger will give you an idea of what to look for and how to solve the problem.

If you find this material too complicated, don't let it bother you. What we aim to provide in this chapter is an example of the routes of attack that you can take, if you choose to pursue the issue. If you aren't inclined to fight with a recalcitrant install, feel free to skip this chapter. There is nothing in the rest of the book that requires that you be comfortable with the troubleshooting material.

At the end of the chapter, we've provided a short section outlining a number of useful applications that you might like to install at the command line. Where possible, we've included copies of the source and compiled binaries on the CD included with this book. In general, the precompiled software will work for you, but if you want the most current and complete version of a piece of software, it's always best to go to the source and build it yourself.



Not a subscriber?

Start A Free Trial

  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint