Article View: gnu.gcc.help
Article #52646gcc under BSD NET2 (Was Re: gcc2.2.2 for 386BSD,success?)
From: rms
Date: Sat, 20 Jun 1992 15:26
Date: Sat, 20 Jun 1992 15:26
20 lines
1562 bytes
1562 bytes
I hope to change GCC in the future to support this system, but I don't have time to do most of the work. If you want to help me do this, please work out a set of changes that I could safely install. In particular, this means you must avoid making changes that would break GCC on other systems. Deleting important code from gstdarg.h is a no-no; likewise, changing libgcc2.c to use stdarg.h instead of gstdard.h is simply unacceptable. (libgcc2.c is compiled with the GCC version being built, and using the system's original stdarg.h file will certainly do the wrongthing on other systems.) Yes, this is more effort than it would take to think only about your own system. But it is the only way that the GCC distribution can be fixed to handle a new system. Short cuts don't produce a result that really contributes to progress. I recommend reading the chapter on Bugs in the GCC manual for advice on how to send in changes to GCC. It has been considerably improved in version 2.2.
Technical Details
Message-ID:
<9206201326.AA05589@lelu.hut.fi>Path:
arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!lelu.hut.fi!rmsShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 11318c,b1c8a643ed755afc X-Google-Attributes: gid11318c,public X-Google-ArrivalTime: 1992-06-19 21:23:10 PST Newsgroups: gnu.gcc.help Path: arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!lelu.hut.fi!rms From: rms@lelu.hut.fi Subject: gcc under BSD NET2 (Was Re: gcc2.2.2 for 386BSD,success?) Message-ID: <9206201326.AA05589@lelu.hut.fi> Sender: daemon@cis.ohio-state.edu Reply-To: rms@gnu.ai.mit.edu Organization: GNUs Not Usenet Distribution: gnu Date: Sat, 20 Jun 1992 15:26:23 GMT Lines: 21