-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
[gmp,nettle,hogweed] Add new ports #10613
Conversation
use --define-variable=prefix=INSTALL_PATH
Note: since CMake is run in script mode the description of VCPKG_FIXUP_PKGCONFIG_CALLED cannot be viewed
CI seems to not pass env YASMPATH correctly to cl. Since YASM is on PATH -> remove $(VCInstallDir) as the default for YasmPath
Hmm:
without failure logs from CI I won't know what went wrong. |
@Neumann-A version msvc ? maybe does not find problem msvc 2019 |
switched to draft until #9861 is merged |
# Conflicts: # scripts/cmake/vcpkg_fixup_pkgconfig.cmake
Requesting a clean rebuild. 3ba8f9f was green and I did not touch anything important since then. The UWP log also looks like an old failure. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Cool, thanks much @Neumann-A :D |
When building
|
No issue here from a clean vcpkg directory. Please delete the old buildtree?. |
@Neumann-A Clone vcpkg in the new directory and run the same command result: same error. |
@Neumann-A I'm having the same error, fwiw |
@Neumann-A looks like yasm is segfaulting |
Hmmm interesting. I went to my Laptop and had the same problem. |
that is... really odd. However, it did work after updating my tools. |
This issue blocked my PR #10767. |
Which VS version is running on CI? |
When using Visual Studio 2019 to build gmp, the error disappeared. |
Describe the pull request
New ports: gmp, nettle (including hogweed)
requires (and includes for CI testing) #9861 (this PR starts at 9307095)
closes #9021
Felt like these should be separated from the X window PR