🚀 go-pugleaf

It is very frustrating for me when people send complaints about GCC
and give only sketchy information about what they have seen.

Often people do this because they don't think of what they are doing
as sending a bug report.  They think they are asking someone else to
tell them what they are doing wrong.

However, any time GCC fails to install straightforwardly on a system
where it is supposed to work, that has a good chance of being due to a
GCC bug.  So, whenever you send a message describing such a case,
always give all the details that might help someone fix the bug.

For example, if you find a symbol that has conflicting declarations,
find the declarations that conflict, and send both of them in your
message, as well as stating which files they are found in.

If you manage to get past one problem only to encounter another, send
full information about both problems.  Just because you found the
cause of the first problem on your own is no reason to make me
duplicate the effort you have already made.  I can hardly keep up with
GCC maintenance in any case; I can't do it unless you do your best to
make it easy.

If the problem turns out not to be a GCC bug, then sending the full
details can only help your chances that someone will send you a
helpful response.