Ryan, two additional paragraphs for the document. please feel to make them more understandable...
Matthias - Revising your build environment (debian/rules file) If you are going to build with gcc-3.2, make sure, that workarounds to build with a specific gcc version on a specific architecture are removed. Some thing for specific optimization settings (like setting -O0, -O1, or -O3). The default flags to build with are "-g -O2". - If the builds fails with the new gcc ... First search the error in your package, not in gcc. Particularly g++-3.2 is more strict to the C++ standard than g++-2.95. XXX reference to an HOWTO? XXX. If you find an internal compiler error (ICE), then submit a bug report. Please look at the error message that gcc emits: in most cases gcc asks for the preprocessed source file to be submitted together with the command line that was used to produce the file. Recompile the file using "-save-temps" and include the (compressed) .i or .ii file in the report. If you want help with debugging, download the gcc-snapshot package and retry compiling your package with this gcc. See see README in the package how this works. In no case, a package built by gcc-snapshot should be uploaded to the archives.