This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
primitive questions
- To: "gcc list (aka egcs)" <gcc at gcc dot gnu dot org>
- Subject: primitive questions
- From: sidster <patrick at mail dot boxsoft dot com>
- Date: Sun, 26 Mar 2000 19:24:11 -0800
Greetings,
I have a couple of what one might call primitive questions regarding
working on the gcc source. I was unable to find answers to my questions
looking through the list (i suppose i didn't know what keywords to search
on to limit the search result).
These questions might be useful as a FAQ entry btw.
Originally I was not going to post to the developer list as to avoid
cluttering developers' inboxes. But I was persuaded to change my mind.
Here goes:
1. When working on the cvs sources for gcc (or other projects e.g.,
libgcj) what is the standard procedure to follow after each of the
following:
a. a `cvs update':
b. source modifications by the developer:
i. is re-running the `configure' script required each time?
ii. does the developer perform the three-stage build of gcc?
(this would seem a bit drastic especially if one has a slower
development box. so I assume there is a different make-target
used for development other than `make bootstrap'.)
Basically I want to know if I were to start tackling the gcc sources
to aid in the bug-fixes, etc. how should I proceed with modifying,
making and testing the changes.
Any pointers to documents available on-line regarding these issues
would be most appreciated.
Best regards,
patrick
p.s., I hope my questions were not too 'silly' to be asked on this list.
--
It's a damn poor mind that can only think of one way to spell a word.
-- Andrew Jackson