On 4 October 2017 at 12:31, nick wrote: > > > On 2017-10-04 06:26 AM, Jonathan Wakely wrote: >> Why are you using gcc-7.0.1? >> > Jonathan, > > This is what the docs stat that command does: > --prefix=dirname > > Specify the toplevel installation directory. This is the recommended way to install the tools into a directory other than the default. The toplevel installation directory defaults to /usr/local. > > We highly recommend against dirname being the same or a subdirectory of objdir or vice versa. If specifying a directory beneath a user’s home directory tree, some shells will not expand dirname correctly if it contains the ‘~’ metacharacter; use $HOME instead. I mean why are you building GCC 7.0.1? That's an unreleased, unsupported snapshot from months and months ago. Possibly buggy. Why not use GCC 7.2? > 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? This has absolutely nothing to do with ccache (which is a completely separate program). The GCC config is very complicated, if you change the config then it's simpler to delete the entire build dir and start again in a completely empty dir. See https://gcc.gnu.org/install/configure.html "If you have previously built GCC in the same directory for a different target machine, do ‘make distclean’ to delete all files that might be invalid. One of the files this deletes is Makefile; if ‘make distclean’ complains that Makefile does not exist or issues a message like “don’t know how to make distclean” it probably means that the directory is already suitably clean. However, with the recommended method of building in a separate objdir, you should simply use a different objdir for each target."
