-
Notifications
You must be signed in to change notification settings - Fork 269
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
Mop up #1084 breakage #1100
Mop up #1084 breakage #1100
Conversation
This reverts commit 5feccf8.
Suggested by Viktor Szakats in libressl#1084
@botovq Thanks for the quick update! Are you sure the This isn't documented (AFAICF) and compiles silently by CMake, but There is a way to add options with inline conditions in certain cases, Or with additional calls to |
Pointed out by @vszakats in libressl#1100
No, of course not :) Now that you point it out, I see the problem... I don't have access to a Windows machine to check. Does #1103 work? |
@botovq #1103 LGTM, thanks! I also don't have a Windows machine to test, and my cross-builds are without DLLs. Reproducing a fitting build locally would be a bit tedious. Within LibreSSL's Windows CI workflow, maybe adding a post-build step doing: find . -name '*.exe' -o -name '*.dll' would add a way to verify this in the logs. |
@vszakats There's an upload build artifact stage in our Windows CI. This one from #1103 shows that the major is actually appended: $ find . -name '*.dll'
./crypto/Release/crypto-55.dll
./ssl/Release/ssl-58.dll
./tests/crypto-55.dll
./tests/ssl-58.dll
./tests/tls-31.dll
./tls/Release/tls-31.dll whereas on HEAD the majors are absent. Thanks for the pointers! https://github.com/libressl/portable/actions/runs/11142580203/artifacts/2005442115 |
@botovq Nice, that also does the job! It's looking good. |
Good catch @botovq, sorry about that. I'm a little baffled how changing the minimum CMake check could actually impact how assembly code is generated though. |
@busterb I suspect it has to do with implicitly enabling more cmake policies. Not sure what it could be though. |
@busterb It compiles the assembly files with Not sure how to fix this. Presumably we need to label the |
@busterb It's actually CMP0119 and we should probably look into using |
Experimented with this, but couldn't find a combination that gets things building when CMP0119 is set to the new behavior. |
Oh, figured out what you meant, testing in #1104 |
On Tue, Oct 08, 2024 at 02:52:22AM -0700, Brent Cook wrote:
Oh, figured out what you meant, testing in #1104
Ah great. Was just about to send a very similar PR. Thanks!
|
Pointed out by @vszakats in libressl#1100
Revert the minimum cmake version change since that isn't viable for major linux distros. Also, it led to weird compilation failures due to some undesirable side effects when compiling assembly files: