You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, ZLIB is not linked to CNPY, which leads to a build error when compiling ABACUS with the DENABLE_CNPY=1 option. The following error is encountered:
/usr/bin/ld: source/module_esolver/CMakeFiles/esolver.dir/io_npz.cpp.o: undefined reference to symbol 'crc32'
/usr/bin/ld: /lib/x86_64-linux-gnu/libz.so.1: error adding symbols: DSO missing from command line
icpx: error: linker command failed with exit code 1 (use -v to see invocation)
Expected behavior
Modify the CMakeLists.txt to correctly link ZLIB with CNPY during the build process. This should resolve the undefined reference to symbol crc32 error and ensure that the build completes successfully.
To Reproduce
No response
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).
The text was updated successfully, but these errors were encountered:
Describe the bug
Currently, ZLIB is not linked to CNPY, which leads to a build error when compiling ABACUS with the
DENABLE_CNPY=1
option. The following error is encountered:Expected behavior
Modify the
CMakeLists.txt
to correctly link ZLIB with CNPY during the build process. This should resolve the undefined reference to symbolcrc32
error and ensure that the build completes successfully.To Reproduce
No response
Environment
No response
Additional Context
No response
Task list for Issue attackers (only for developers)
The text was updated successfully, but these errors were encountered: