Just wanted to say, I saw the recent commits to improve INSTALL.md, and I really appreciate them.  Thank you. :D

  I'm new to forth, so at the time it never occurred to me that one of the dependencies of the "build-from-source" version would be the outdated version of gforth.  (Which I now understand, as forth is traditionally self-hosted.)  I just assumed that following the instructions would end up with the latest version added to the path, and it never occurred to me that I'd have any reason to follow the tarball instructions.
  I guess I didn't expect building something from source to result in multiple versions being installed.  Perhaps we could make this more user-friendly by defaulting to the "build from tarball" option.
  But in the meantime, we can probably close this bug report, since there isn't a bug per-say.  We could probably improve the build process, but that's another discussion.  I appreciate the discourse & responsiveness, especially as I'm pretty new to forth and will likely have more questions in the future.

  That's good to know, I'll try using the "tarball" option later today when I get the chance.  Still, it would be nice if the INSTALL.md instructions at least explained this to you.

  Including the tarball could help, but perhaps this problem could be solved by using a "chroot" environment.  Just install the older Gforth within that "chroot" environment, so that only the newer Gforth will end up installed on the host system.
  Admittedly, I don't have any experience using the "chroot" command, so maybe it wouldn't work here, but I'll check it out and see if it does.
(Also, now I have an account.  Woo! :D)