Although there's no problem when installing ABACUS with toolchain, this behavior will break the generation of module file (via module sh-to-mod bash abacus_env.sh), caussing many other environment variables like LD_LIBRARY_PATH missing, which is obviously necessary for normally running ABACUS.
I'm curious about why the export PATH is used again after prepend_path PATH function, which has already included the export PATH command? Moreover, since prepend_path has the logic to bypass the duplication, I don't think manually exporting the paths after prepend_path has run is correct; it is risky and would cause only issues in my view.
Although there's no problem when installing ABACUS with toolchain, this behavior will break the generation of module file (via
module sh-to-mod bash abacus_env.sh), caussing many other environment variables likeLD_LIBRARY_PATHmissing, which is obviously necessary for normally running ABACUS.I'm curious about why the
export PATHis used again afterprepend_path PATHfunction, which has already included theexport PATHcommand? Moreover, sinceprepend_pathhas the logic to bypass the duplication, I don't think manually exporting the paths afterprepend_pathhas run is correct; it is risky and would cause only issues in my view.