CrossGCC Frequently Asked Questions: How to get help

If the topic is related to using the tools in a cross-compiler environment then this list is an excellent place to look for help. If you've found a bug in a particular piece of software, it is best to report the bug to the appropriate list (e.g. bug-gcc) rather than this list.

Be careful about reporting bugs associated with patches you have applied to GCC (or any GNU software). The FSF has not sanctioned these patches and shouldn't have to respond to bug reports for such patches. Sometimes it is hard to tell, in which case use your best judgement. When sending bug reports to bug-gcc, always mention all patches applied.

11.2 Online documentation

Documentation for the GNU tools as packaged by Cygnus may be found in http://www.cygnus.com/pubs/gnupro. Documentation for the FSF releases, along with other stuff useful to embedded developers, may be found at http://www.sthoward.com/docs.

11.3 Web sites

Binutils:: http://sourceware.cygnus.com/binutils
GCC/G++:: http://egcs.cygnus.com/
Glibc:: http://www.gnu.org/software/libc
Gdb:: http://sourceware.cygnus.com/gdb
Newlib:: http://sourceware.cygnus.com/newlib

11.4 Bug reporting

Here is a list of the tools and their bug reporting addresses:

Binutils:: bug-gnu-utils@gnu.org
GCC:: bug-gcc@gnu.org
G++:: bug-g++@gnu.org
Glibc:: bug-glibc@gnu.org
GDB:: bug-gdb@gnu.org
Newlib:: newlib@sourceware.cygnus.com

When reporting a bug, please read the documentation that comes with the software to find out how to report a bug. If you've installed `info' and the GCC info files, `info -f gcc.info -n Bugs' should zip you right to the page you need to read for GCC. Failing that, always include the following information:

version number (e.g. gcc-2.95.2)
configuration (the arguments you passed to `configure')
type of system you are compiling on (e.g. i386-linux, sparc-solaris2); ideally this is the result of the `config.guess' program that is included in the source tree
(in the case of gas, gcc, glibc, and newlib) preprocessed source that triggers the bug. Preprocessed source can either be obtained by passing -E to GCC and sending the output, or by passing -save-temps to GCC and sending the resulting .i file (or .ii file in the case of g++). It is generally much better to include the preprocessed source rather than say `GCC can't compile file foo.c from program Bar version 4.2'.
complete list of options passed to the program (e.g. gcc -g -O2 ...).
the text of the error message (as output by the program, do not edit it for brevity)