Linking error during MA5 installation: MA5-ERROR: impossible to link the project

Hi, I've been trying to install a newer version of MA5 to interface with MG5 v2.6.5. After having a working installation of MA5 v1.6, I found that it was not directly compatible with my version of MG5 and opted to update MA5 manually (updating through MG5 has not been working properly). However, after removing v1.6 and installing 1.7 to see if this would fix compatibility with MG5, I began to run into this error upon first run of ./bin/ma5:

MA5-ERROR: impossible to link the project. For more details, see the log file:
MA5-ERROR: /misc/raid03/users/alecp1/MG5_aMC_v2_6_5/HEPTools/madanalysis5/madanalysis5/tools/SampleAnalyzer/Test//linking_root.log
MA5-ERROR: The test program building aborted.

Components 1-8/11 while building the sample libraries all succeeded, except for this, the 9th (test program: interface to Root). This problem persists though all major releases of MA5 I've tried, even when retrying an installation of v1.6 which had initially worked. It also persists when vetoing root in installation_options.dat. The contents of the linking_root.log are:

g++ Root/Test.o -L/misc/raid03/users/alecp1/MG5_aMC_v2_6_5/HEPTools/madanalysis5/madanalysis5/tools/SampleAnalyzer/Li
b -L/misc/raid03/users/alecp1/MG5_aMC_v2_6_5/HEPTools/madanalysis5/madanalysis5/tools/SampleAnalyzer/ExternalSymLink/L
ib -lroot_for_ma5 -L/cvmfs/sft.cern.ch/lcg/releases/ROOT/v6.20.06-3f7fd/x86_64-centos7-gcc8-opt/lib -lCore -lImt -lRIO
 -lNet -lHist -lGraf -lGraf3d -lGpad -lROOTVecOps -lTree -lTreePlayer -lRint -lPostscript -lMatrix -lPhysics -lMathCor
e -lThread -lMultiProc -lROOTDataFrame -pthread -lm -ldl -rdynamic -lEG -lcommons_for_ma5 -L/cvmfs/sft.cern.ch/lcg/rel
eases/ROOT/v6.20.06-3f7fd/x86_64-centos7-gcc8-opt/lib -lCore -lImt -lRIO -lNet -lHist -lGraf -lGraf3d -lGpad -lROOTVec
Ops -lTree -lTreePlayer -lRint -lPostscript -lMatrix -lPhysics -lMathCore -lThread -lMultiProc -lROOTDataFrame -pthrea
d -lm -ldl -rdynamic -lEG -o ../Bin/TestRoot
/cvmfs/sft.cern.ch/lcg/releases/ROOT/v6.20.06-3f7fd/x86_64-centos7-gcc8-opt/lib/libImt.so: undefined reference to `tbb
::interface7::internal::task_arena_base::internal_terminate()'
/cvmfs/sft.cern.ch/lcg/releases/ROOT/v6.20.06-3f7fd/x86_64-centos7-gcc8-opt/lib/libImt.so: undefined reference to `tbb
::interface7::internal::isolate_within_arena(tbb::interface7::internal::delegate_base&, long)'
/cvmfs/sft.cern.ch/lcg/releases/ROOT/v6.20.06-3f7fd/x86_64-centos7-gcc8-opt/lib/libImt.so: undefined reference to `tbb
::interface7::internal::task_arena_base::internal_initialize()'
/cvmfs/sft.cern.ch/lcg/releases/ROOT/v6.20.06-3f7fd/x86_64-centos7-gcc8-opt/lib/libImt.so: undefined reference to `tbb
::interface7::internal::task_arena_base::internal_execute(tbb::interface7::internal::delegate_base&) const'
collect2: error: ld returned 1 exit status
make: *** [link] Error 1

If it helps any, during the first (working) installation of v1.6, I had to install a number of packages using MA5, but even after removing the entire directory, subsequent installations maintained that those packages still existed, which I found odd.

I'm guessing this has something to do with some sort of persistent environment variable or something to that tune, but I'm not sure what it could be, and my experience in unix-systems is very limited. Any thoughts?