wow, I never went as far as actually check the version that's specified as a dependency...

There's no need to though: there's no way another GCC version can be loaded without you knowing. If an other version was already loaded before the build starts, the "module load GCC" done for the listed dependency would fail due to a conflict, and so the build would exit early.