G. Installing Pintos

This chapter explains how to install a Pintos development environment on your own machine. If you are using a Pintos development environment that has been set up by someone else, you do not need to read this chapter or follow these instructions.

The Pintos development environment is targeted at Unix-like systems. It has been most extensively tested on Linux. We do not support running Pintos on Solaris or architectures other that x86/x86-64. It is not designed to install under any form of Windows.

Prerequisites for installing a Pintos development environment include the following, on top of standard Unix utilities:

• Required: GCC. Version 4.6 or later is preferred. If the host machine has an 80x86 processor, then GCC should be available as gcc; otherwise, an 80x86 cross-compiler should be available as i386-elf-gcc. A sample set of commands for installing GCC 3.3.6 as a cross-compiler are included in src/misc/gcc-3.3.6-cross-howto.

• Required: GNU binutils. Pintos uses addr2line, ar, ld, objcopy, and ranlib. If the host machine is not an 80x86, versions targeting 80x86 should be available with an i386-elf- prefix.

• Required: Perl. Version 5.14 or later is preferred.

• Required: GNU make, version 3.80 or later.

• Required: a virtual machine
  • Supported: QEMU, version 0.14 or later.
  • Optional: VMware Player.
  • Optional: Bochs, version 2.2.6. Install as described in H.1 Building Bochs for Pintos.
  • Optional: Install a more up-to-date version of Bochs provided by your own distribution. You may have modify the pintos script and tell it where to find the various Bochs binaries on your system.

• Recommended: GDB. GDB is helpful in debugging (see section E.5 GDB). If the host machine is not an 80x86, a version of GDB targeting 80x86 should be available as i386-elf-gdb.

Once these prerequisites are available, follow these instructions to install Pintos:

1. Update your PATH as described in section 1.1 Getting Started. Then use a text editor to edit the installed copy of pintos-gdb, changing the definition of GDBMACROS to point to where you installed gdb-macros. Test the installation by running pintos-gdb without any arguments. If it does not complain about missing gdb-macros, it is installed correctly.

2. Compile the Pintos utilities by typing make in src/utils. Bochs needs squish-pty, VMware Player needs squish-unix. If they don't compile on your recent Linux distribution, comment out #include <stropts.h> in both squish-pty.c and squish-unix.c, and comment out lines 288-293 in squish-pty.c.

3. Pintos should now be ready for use. If the system doesn't find the qemu binary, modify the line my (@cmd) = ('qemu'); in src/utils/pintos::sub qemu to point to your qemu binary (for example, qemu-system-x86_64), or simply create a qemu -> qemu-system-x86_64 symbolic link.