On 04/10/17 12:31, nick wrote:
Care to explain how that's an issue when not installing gcc and
just running the test suite? Also care to explain how ccache
fails everything I run a change to my build config?
For what is worth, there are thousands of things that can fail when building
GCC and it is very easy to make a mess out of it.
My advice is to follow the docs to the letter and script everything that you do
so you can easily start from zero and do the steps again.
Start here:
https://gcc.gnu.org/wiki/GettingStarted#Basics:_Contributing_to_GCC_in_10_easy_steps
Check also here: https://gcc.gnu.org/wiki/FAQ
My personal build+test script is here:
https://gcc.gnu.org/wiki/ManuelL%C3%B3pezIb%C3%A1%C3%B1ez?action=AttachFile&do=view&target=gccfarming
It may be a bit outdated and it is designed for the GCC Compile Farm, but it
may give you ideas for creating your own. If you are testing a fix, the most
robust approach (and the one followed by my script) is to have a pristine copy
of the source tree and a pristine build and, separately, a patched version of
the source tree and a patched build.
I hope this helps,
Manuel.
