[Code scan] Use the same SuperLU_DIST32_ROOT variable in CI path exports

[njzjz]

This issue is a result of a Codex global repository scan.

Some CI path exports use SUPERLU32_DIST_ROOT, while the same command block uses SUPERLU_DIST32_ROOT in CMAKE_PREFIX_PATH. If only the latter variable is defined, LD_LIBRARY_PATH, PKG_CONFIG_PATH, and CPATH omit SuperLU_DIST while CMake receives a different variable name.

Build test workflow:

abacus-develop/.github/workflows/build_test_cmake.yml

Lines 50 to 56 in 84ca04b

	- name: Build
	run: |
	git config --global --add safe.directory `pwd`
	export LD_LIBRARY_PATH=${GKLIB_ROOT}/lib:${METIS32_ROOT}/lib:${PARMETIS32_ROOT}/lib:${SUPERLU32_DIST_ROOT}/lib:${PEXSI32_ROOT}/lib:${LD_LIBRARY_PATH}
	export PKG_CONFIG_PATH=${GKLIB_ROOT}/lib/pkgconfig:${METIS32_ROOT}/lib/pkgconfig:${PARMETIS32_ROOT}/lib/pkgconfig:${SUPERLU32_DIST_ROOT}/lib/pkgconfig:${PEXSI32_ROOT}/lib/pkgconfig:${PKG_CONFIG_PATH}
	export CPATH=${GKLIB_ROOT}/include:${METIS32_ROOT}/include:${PARMETIS32_ROOT}/include:${SUPERLU32_DIST_ROOT}/include:${PEXSI32_ROOT}/include:${CPATH}
	export CMAKE_PREFIX_PATH=${PEXSI32_ROOT}:${SUPERLU_DIST32_ROOT}:${PARMETIS32_ROOT}:${METIS32_ROOT}:${GKLIB_ROOT}:${CMAKE_PREFIX_PATH}

ASE plugin workflow:

abacus-develop/.github/workflows/ase_plugin_test.yml

Lines 36 to 42 in 84ca04b

	- name: Configure & Build ABACUS (GNU)
	run: |
	git config --global --add safe.directory `pwd`
	export LD_LIBRARY_PATH=${GKLIB_ROOT}/lib:${METIS32_ROOT}/lib:${PARMETIS32_ROOT}/lib:${SUPERLU32_DIST_ROOT}/lib:${PEXSI32_ROOT}/lib:${LD_LIBRARY_PATH}
	export PKG_CONFIG_PATH=${GKLIB_ROOT}/lib/pkgconfig:${METIS32_ROOT}/lib/pkgconfig:${PARMETIS32_ROOT}/lib/pkgconfig:${SUPERLU32_DIST_ROOT}/lib/pkgconfig:${PEXSI32_ROOT}/lib/pkgconfig:${PKG_CONFIG_PATH}
	export CPATH=${GKLIB_ROOT}/include:${METIS32_ROOT}/include:${PARMETIS32_ROOT}/include:${SUPERLU32_DIST_ROOT}/include:${PEXSI32_ROOT}/include:${CPATH}
	export CMAKE_PREFIX_PATH=${PEXSI32_ROOT}:${SUPERLU_DIST32_ROOT}:${PARMETIS32_ROOT}:${METIS32_ROOT}:${GKLIB_ROOT}:${CMAKE_PREFIX_PATH}

Relevant code:

export LD_LIBRARY_PATH=...:${SUPERLU32_DIST_ROOT}/lib:...
export PKG_CONFIG_PATH=...:${SUPERLU32_DIST_ROOT}/lib/pkgconfig:...
export CPATH=...:${SUPERLU32_DIST_ROOT}/include:...
export CMAKE_PREFIX_PATH=${PEXSI32_ROOT}:${SUPERLU_DIST32_ROOT}:...

Suggested fix:

Use one variable spelling consistently, likely SUPERLU_DIST32_ROOT, in all exported paths and setup steps.

[Growl1234]

If SuperLu can be detected through CMAKE_PREFIX_PATH, all other exported variables should be dropped.

Since PEXSI can (and is recommended to) be built with CMake and export CMake configuration file, the FindPEXSI.cmake should be dropped as well, which would definitely make the workflow much cleaner.