2.2.3 Using Multiple Source Files
2.4.2 Separate Compiling and Linking
2.4.3 Consistent Compiling and Linking
2.4.4 Compiling for 64-Bit Memory Model
2.4.5 Compiler Command-Line Diagnostics
2.4.6 Understanding the Compiler Organization
2.5 Preprocessing Directives and Names
2.5.2 Macros With a Variable Number of Arguments
2.6.3 Control of Virtual Memory
2.7 Using the strip Command with C++ Objects
2.8.1 Using Aliases Within the C Shell
2.8.2 Using CCFLAGS to Specify Compile Options
2.8.3.1 Using CCFLAGS Within make
3. Using the C++ Compiler Options
6. Creating and Using Templates
9. Improving Program Performance
10. Building Multithreaded Programs
12. Using The C++ Standard Library
13. Using the Classic iostream Library
This compiler does not use the cache by default. It only uses the cache if you specify -instances=extern. If the compiler makes use of the cache, it checks the cache directory’s version and issues error messages whenever it encounters cache version problems. Future C++ compilers will also check cache versions. For example, a future compiler that has a different template cache version identification and that processes a cache directory produced by this release of the compiler might issue an error that is similar to the following message:
Template Database at ./SunWS_cache is incompatible with this compiler
Similarly, the compiler issues an error if it encounters a cache directory that was produced by a later version of the compiler.
When you upgrade your compiler, it is always good practice to clean the cache. Run CCadmin -clean on every directory that contains a template cache directory (in most cases, a template cache directory is named SunWS_cache). Alternatively, you can use rm -rf SunWS_cache.