This chapter discusses the purpose of build flavors and how they can be used. An important GPT convention is the format of the flavor label. This label is used in both package and file names. The figure here shows the components of a typical flavor name. The conventions is that any component that has the value none will contribute nothing to the label. The table here shows possible values of the flavor components. This table shows some examples
Table 2.1. Flavor Components
| Component | Values | Label | Description |
|---|---|---|---|
| Compiler | gcc | gcc | Use the GNU C compiler |
| vendorcc | vendorcc | Use the C compiler provided by the platform vendor. | |
| mpicc | mpicc | Use the wrapper script for the C compiler provided by MPI. | |
| Number Size | 32 | 32 | Compile with 32 bit integers |
| 64 | 64 | Compile with 64 bit integers | |
| Debug | dbg | dbg | Have the compiler produce debugging data inside the binary |
| nodbg | Binary will not contain debugging data. | ||
| Threads | pthr | pthr | Compiler creates binaries that use pthreads |
| solaristhreads | solthr | Compiler creates binaries that use solaris native threads | |
| nothreads | Compiler creates binaries that are not guaranteed to be thread safe. |