[Bug]Errors in the building process of abacus with pexsi support #6684
Description
Describe the bug
[ 41%] Building CXX object source/source_estate/CMakeFiles/elecstate.dir/module_dm/init_dm.cpp.o
/tmp/abacus-develop/source/source_estate/elecstate_lcao.cpp:36:29: error: out-of-line definition of 'dm2Rho' does not match any declaration in 'elecstate::ElecStateLCAO'; did you mean 'dm2rho'?
36 | void ElecStateLCAO::dm2Rho(std::vector<double*> pexsi_DM, std::vector<double*> pexsi_EDM)
| dm2rho
/tmp/abacus-develop/source/source_estate/elecstate_lcao.cpp:36:29: note: 'dm2rho' declared here
/tmp/abacus-develop/source/source_estate/elecstate_lcao.cpp:46:11: error: no member named 'get_DM' in 'elecstate::ElecStateLCAO'
46 | this->get_DM()->pexsi_EDM = pexsi_EDM;
/tmp/abacus-develop/source/source_estate/elecstate_lcao.cpp:50:15: error: no member named 'DM' in 'elecstate::ElecStateLCAO'
50 | this->DM->set_DMK_pointer(is, pexsi_DM[is]);
/tmp/abacus-develop/source/source_estate/elecstate_lcao.cpp:52:5: error: use of undeclared identifier 'DM'
52 | DM->cal_DMR();
/tmp/abacus-develop/source/source_estate/elecstate_lcao.cpp:61:36: error: no member named 'DM' in 'elecstate::ElecStateLCAO'
61 | ModuleGint::cal_gint_rho(this->DM->get_DMR_vector(), PARAM.inp.nspin, this->charge->rho);
/tmp/abacus-develop/source/source_estate/elecstate_lcao.cpp:68:40: error: no member named 'DM' in 'elecstate::ElecStateLCAO'
68 | ModuleGint::cal_gint_tau(this->DM->get_DMR_vector(), PARAM.inp.nspin, this->charge->kin_r);
6 errors generated.
Expected behavior
No response
To Reproduce
DockerFile.intel
Environment
No response
Additional Context
No response
Task list for Issue attackers (only for developers)
- Verify the issue is not a duplicate.
- Describe the bug.
- Steps to reproduce.
- Expected behavior.
- Error message.
- Environment details.
- Additional context.
- Assign a priority level (low, medium, high, urgent).
- Assign the issue to a team member.
- Label the issue with relevant tags.
- Identify possible related issues.
- Create a unit test or automated test to reproduce the bug (if applicable).
- Fix the bug.
- Test the fix.
- Update documentation (if necessary).
- Close the issue and inform the reporter (if applicable).