non-standard path gcc compile googltest failed in centos7 about xmipp HOT 1 CLOSED

Hey @wsatbluesky! Sorry for the late response. In the future, for quicker answers, we are usually way quicker answering in Scipion's Discord Server, there is a channel for Xmipp there.

Regarding your issue:
What xmipp is doing to build googletest:

• Goes to your xmipp's directory, and inside to src/googletest, creates a build directory, and moves inside it.
• Then runs: cmake .. and, if that command succeeds, runs make gtest gtest_main.
  So, Xmipp is properly detecting your odd gcc/g++ installation path, but it's cmake the one switching to the default installation.

What you can do to test this:

• Go to your xmipp's directory, in production versions, this is located inside your scipion folder, in software/em. To further develop this, go to your scipion directory, and from there, if your are on the latest production version (v3.23.07.0 as of today), cd to software/em/xmippSrc-v3.23.07.0 (if your are on a different version, it's xmippSrc-whateverVersion, just changing the version variable).
• Once there, move to src/googletest.
• Run ls. If build directory exists (it probably should) cd build, else mkdir build && cd build.
• Then, run cmake ... This command should generate a Makefile inside build folder, try to open it and check the references it might have to gcc.
• Finally run make gtest gtest_main, if your gcc location is fine, this should work, but I'm guessing cmake will find your default gcc, therefore, creating the problem you described.
• If the error occurs, run echo $CC && echo $CXX, which contain the paths to the gcc/g++ cmake will use. If they are not the desired ones, you might be able to fix your installation by simply overriding those values with export inside your .bashrc (export CC=/path/to/your/gcc && export CXX=/path/to/your/g++)

Let me know if this worked!

from xmipp.