Amber masthead
Filler image AmberTools22 Amber22 Manuals Tutorials Force Fields Contacts History
Filler image

Useful links:

Amber Home
Download Amber
Amber Citations
GPU Support
Mailing Lists
For Educators
File Formats

Amber Bug Fixes and Updates

Patches for AmberTools and patches for the flagship Amber software are now listed on two separate pages, with the most recent patches appearing first. 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, but in general each page is a big stack of details showing how Amber has been fixed over the years. The best way to apply patches is permit the updater to run automatically when running configure, the first step of the installation process. These chronicles of bug fixes are written for code wonks and should be text searched with Ctrl + F or the equivalent command on your system; mostly we expect you will use them to determine if an old version of Amber is sufficient and safe 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 Reference Manuals. bugfix.X files contain context diffs. The format of these is:

***old version
---new version

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 patchfile

If a file file_to_be_patched.rej is created, examine it, read the patch main 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.

"How's that for maxed out?"

Last modified: May 3, 2020