These pages include both traditional "bug fixes", along with various updates, such as Machine files for new compilers or architectures, that would not ordinarily be considered as "bugs". The short descriptions should help you decide which patches are relevant for your needs.
Each bugfix contains a description of the problem and patches to fix the code. Also check the Manual Updates page for revisions to the version 12 Reference Manuals. (Click here for updates to the Amber11 manuals.)
***old version "code" ---new version "code"where 3 lines of unmodified code are included before and after each modified section. Changed lines are denoted by a '!', added lines by a '+', and deleted lines by a '-'. These diffs contain sufficient information to fix things by hand. Alternatively, if the Unix patch(1) program is available, the diff for each file can be put in its own file (patchfile) and patch run as follows:
% cp file_to_be_patched file.backup % patch -c file_to_be_patched patchfileIf a file file_to_be_patched.rej is created, examine it, read the patch man page, consider whether previous fixes may not have been applied, and panic at your leisure. As a partial check on the cumulative patching activity, after recompiling any affected code you can run the test scripts.