FW: GNU Mailing Lists Question #1

[James E Wilson]

Chris Miller wrote:
> Hi.  I'm hoping you can help me with the questions in this e-mail and the
> one that follows. 

Bugs should be reported into bugzilla.  Period.  The old info is 
obsolete and should be ignored.  See
     http://gcc.gnu.org/bugs.html

Mailing list info can be found here:
     http://gcc.gnu.org/lists.html
The old info is obsolete and should be ignored.

We aren't interested in bug reports against gcc releases older than 
gcc-3.3.  Any such bugs will be closed without further comment if the 
problem is already fixed in current releases.

We are especially not interested in bug reports against proprietary gcc 
releases, where proprietary means any release not made by the FSF.  If 
you have made any modifications to the gcc sources you are releasing, 
then we don't want the bug reports.  Any such bugs will be closed with a 
comment telling the reporter to contact the vendor that produced their 
gcc release.  See the tenth bullet at
     http://gcc.gnu.org/bugs.html#dontwant

If you are making a proprietary release, there are a few things you 
should do to the gcc sources.  I don't think we have a documented list 
of them, but I think there are only two main ones:
a) Change the version number to indicate where it came from, e.g. 
something like "gcc 2.95 (lnxw)" instead of just "gcc 2.95".  Try "gcc 
-v" on most any linux system for comparison.
b) Change the message printed when an internal error is detected. 
Instead of mentioning the gcc.gnu.org address, it should point at an 
address inside lnxw.com.  Where this message exists depends on the gcc 
version you have, which you didn't mention.  Look at GCCBUGURL in 
system.h in gcc-2.95, look at bug_report_url in version.c in current 
releases.
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com