I'm trying to understand the aftermath of a failed gcc compile attempt. I think I know WHY it failed (I didn't patch), I just dont understand why that would produce the things in my tools folder. Further, since I want to keep the binutils compile that seemed to work, how can I clean up the aftermath of the GCC compile attempt without wiping out what binutils put in? This is what I see inside tools:

bin file
lib folder with empty directories that end with a gcc readme
libexec folder with empty directories that end with a gcc readme

So, im assuming I need to somehow "slice" the gcc from the bin file without touching the binutils somehow?

I'm sure I could just get rid of tools and start over, since binutils was quick and easy, but I want to understand whats happening with greater detail.

Not sure if my answer is any clearer than your question... ;-)

Since gcc did not compile, it did not install, right?
I assume you built it in "gcc-build" directory.
If so, removing everithing from this directory [or trying "make distclean" first and seeing if it doesn't end with en error], patching and configuring it again will help.