Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BLAS][LAPACK] Add Netlib in PATH for Windows testing #252

Open
dnhsieh-intel opened this issue Nov 22, 2022 · 0 comments
Open

[BLAS][LAPACK] Add Netlib in PATH for Windows testing #252

dnhsieh-intel opened this issue Nov 22, 2022 · 0 comments
Labels
build A request to change/fix/improve the build system help wanted Tasks, issues or features that could be implemented and contributed to the project

Comments

@dnhsieh-intel
Copy link
Contributor

Problem statement

To build Windows testing for BLAS and LAPACK domains, users would need to add Netlib in the environment variable PATH manually. Otherwise, the executables test_main_<domain>_rt.exe and test_main_<domain>_ct.exe would fail to build at linking. If the build is successful and users run tests later in a separate session, they would need to add Netlib in PATH again, or tests might fail due to Netlib library not found.

The requirement of Netlib in PATH for Windows testing is missing in README.

Preferred solution

Since the Netlib directories ${CBLAS_LIB_DIR} and ${LAPACKE64_LIB_DIR} are readily available, a preferred solution would be to integrate them in CMake files so that users can skip the step of setting up PATH for Netlib.

Note

As discussed in one PR comment, updating PATH for Windows testing might need a workaround.

@mkrainiuk mkrainiuk added build A request to change/fix/improve the build system help wanted Tasks, issues or features that could be implemented and contributed to the project labels Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build A request to change/fix/improve the build system help wanted Tasks, issues or features that could be implemented and contributed to the project
Projects
None yet
Development

No branches or pull requests

2 participants