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] Build error #22045

Open
stalek71 opened this issue Dec 15, 2021 · 12 comments
Open

[lapack] Build error #22045

stalek71 opened this issue Dec 15, 2021 · 12 comments
Assignees
Labels
category:port-bug The issue is with a library, which is something the port should already support

Comments

@stalek71
Copy link

Host Environment

  • OS: Windows 11, Windows Server 2022
  • Compiler: MSVC 19.30.30706 for x64 (installed as a part of the latest VS 2022).

To Reproduce
Steps to reproduce the behavior:
./vcpkg install lapack[core]:x64-windows

Failure logs

CMake Error at P:/vcpkg/installed/x64-windows/share/lapack/FindLAPACK.cmake:522 (message):
  A required library with LAPACK API not found.  Please specify library  location.
Call Stack (most recent call first):
  P:/vcpkg/installed/x64-windows/share/lapack/vcpkg-cmake-wrapper.cmake:9 (_find_package)
  P:/vcpkg/scripts/buildsystems/vcpkg.cmake:742 (include)
  CMakeLists.txt:4 (find_package)

Additional context
The configuration is the same: clear system with latest VS 2022, VCPKG and git.

@JackBoosY JackBoosY added the requires:repro The issue is not currently repro-able label Dec 16, 2021
@JackBoosY
Copy link
Contributor

Can you please confirm your vcpkg is latest?

Thanks.

@JackBoosY JackBoosY added the requires:more-information This Issue requires more information to solve label Dec 16, 2021
@stalek71
Copy link
Author

Yes, it's in the latest version (taken yesterday)

@stalek71
Copy link
Author

The same issue is on a new virtual machine based on Win 10 Pro.
I attached log files to this message

CMakeError.log
config-x64-windows-out.log
CMakeOutput.log

@JackBoosY JackBoosY removed the requires:more-information This Issue requires more information to solve label Dec 17, 2021
@JackBoosY
Copy link
Contributor

Very sorry for late, I will handle this first.

@JackBoosY
Copy link
Contributor

Can you provide the file list in VCPKG_ROOT/packages/lapack-reference_x64-windows/debug/lib and VCPKG_ROOT/packages/openblas_x64-windows/debug/lib?
There must have something unexpected.

@JackBoosY JackBoosY added the requires:more-information This Issue requires more information to solve label Jan 12, 2022
@stalek71
Copy link
Author

obraz

obraz

@JackBoosY
Copy link
Contributor

Okay, I think we should wait for #21479 merge, then handle this issue if it still exist.

@JackBoosY JackBoosY removed the requires:more-information This Issue requires more information to solve label Jan 18, 2022
@stalek71
Copy link
Author

It looks nothing changed up to now...

obraz

@andieis
Copy link

andieis commented Feb 24, 2022

I'm encountering the exact same problem as @stalek71. So I'm wondering, when the merge of #21479 will happen. Will it be approximately in 2 weeks or 5 months or ...? Thanks a lot in advance vor your work!

@JackBoosY
Copy link
Contributor

@ras0219-msft do you have any plan to complete #21479?

@JackBoosY JackBoosY added category:port-bug The issue is with a library, which is something the port should already support and removed requires:repro The issue is not currently repro-able labels Aug 5, 2022
@LilyWangLL LilyWangLL assigned LilyWangLL and unassigned JackBoosY Dec 6, 2022
Copy link

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 Stale and removed Stale labels Jul 25, 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
Projects
None yet
Development

No branches or pull requests

5 participants
@stalek71 @andieis @JackBoosY @LilyWangLL and others