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

[lapack-reference] Cannot disable blas-select on Linux #21224

Closed
cgmb opened this issue Nov 6, 2021 · 2 comments
Closed

[lapack-reference] Cannot disable blas-select on Linux #21224

cgmb opened this issue Nov 6, 2021 · 2 comments
Assignees
Labels
category:port-bug The issue is with a library, which is something the port should already support Stale

Comments

@cgmb
Copy link

cgmb commented Nov 6, 2021

Describe the bug
On Linux, USE_OPTIMIZED_BLAS=ON appears to always be set when using an external Fortran compiler, but it should only be true when using the blas-select or noblas features.

Environment

  • OS: Linux (Ubuntu 18.04)
  • Compiler: gfortran

To Reproduce
I created a project to illustrate the problem. It sets "default-features": false to disable blas-select.

Steps to reproduce the behavior:

  1. Download the example project: https://gist.github.com/cgmb/371a8279ee5bc8f63285d0b96d920a41
  2. Configure the project.
cmake -S. -Bbuild -DCMAKE_TOOLCHAIN_FILE=$VCPKG_PATH/scripts/buildsystems/vcpkg.cmake -DVCPKG_TARGET_TRIPLET=x64-linux
  1. Examine the lapack-reference build parameters:
grep USE_OPTIMIZED_BLAS $VCPKG_PATH/buildtrees/lapack-reference/x64-linux-rel/CMakeCache.txt

Actual Output:

USE_OPTIMIZED_BLAS:BOOL=ON

Expected Output:

USE_OPTIMIZED_BLAS:BOOL=OFF
@PhoebeHui PhoebeHui added the category:port-bug The issue is with a library, which is something the port should already support label Nov 8, 2021
@PhoebeHui
Copy link
Contributor

@cgmb,t thanks for reporting this issue! Could you help test linked PR and see if it works for you?

Copy link

github-actions bot commented Aug 5, 2024

This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 180 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment.

@github-actions github-actions bot added the Stale label Aug 5, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-bug The issue is with a library, which is something the port should already support Stale
Projects
None yet
2 participants