Bundle easyblock with `--module-only` not consistent

[ocaisa]

When rebuilding the EESSI stack module tree with --module-only I noticed that the GCC module was not consistent (GCC uses the bundle easyblock):

diff --git a/GCC/9.3.0.lua b/GCC/9.3.0.lua
index c5ba715..9d36c56 100644
--- a/GCC/9.3.0.lua
+++ b/GCC/9.3.0.lua
@@ -24,9 +24,8 @@ if not ( isloaded("GCCcore/9.3.0") ) then
     load("GCCcore/9.3.0")
 end
 
-prepend_path("CMAKE_PREFIX_PATH", root)
-setenv("EBROOTGCC", root)
+setenv("EBROOTGCC", "/cvmfs/pilot.eessi-hpc.org/2021.03/software/linux/x86_64/amd/zen2/software/GCCcore/9.3.0")
 setenv("EBVERSIONGCC", "9.3.0")
 setenv("EBDEVELGCC", pathJoin(root, "easybuild/GCC-9.3.0-easybuild-devel"))

[boegel]

Hmm, since CMAKE_PREFIX_PATH is not getting set, this may actually be a bug in framework?

[ocaisa]

There was a difference between those builds: EB 4.3.3 and EB 4.3.4

[boegel]

EasyBuild v4.3.3 instead also updated $CMAKE_PREFIX_PATH for GCC-9.3.0.eb, but that doesn't make much sense (since the installation directory is empty). So this isn't really a bug imho?

I think the difference between updating $CMAKE_PREFIX_PATH or not is triggered by having a non-empty installation directory for GCC, since the easybuild directory (which includes the copy of the log file) is in there?