https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116730
--- Comment #5 from Hime Haieto <himehaieto at gmail dot com> --- This is the same process I've used for every past version of gcc, every autotools project that isn't completely broken by abusing the autotools environment/standards, as well as most projects that don't use autotools (e.g., cmake). I've never seen a situation where a project is using autotools and relative paths work as they should, but somehow it expects/requires any specific structure to that relative path other than perhaps not being contained within the source tree in some niche cases. Both ../dir and ../../dir (and .././../dir/../dir) are relative paths and should work the exact same unless any relative paths are hardcoded in the build files (at which point all builds break, relative or absolute, unless the build directory is in exactly the same relative location from the source...an unlikely sight). In any case, I'm highly skeptical that is related to the issue here. What I have not tested due to build times is if it works when done in one go (i.e., configure/make install instead of configure/make/make install). This could be a likely possibility.
