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

[libressl] Update to v4.0.0 #42145

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

donny-dont
Copy link
Contributor

  • Changes comply with the maintainer guide.
  • SHA512s are updated for each updated download.
  • The "supports" clause reflects platforms that may be fixed by this new version.
  • Any fixed CI baseline entries are removed from that file.
  • Any patches that are no longer applied are deleted from the port's directory.
  • The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
  • Only one version is added to each modified port's versions file.

@donny-dont
Copy link
Contributor Author

First time updating a port so happy to do whatever is needed to land this.

Copy link
Contributor Author

@donny-dont donny-dont left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just adding some notice on upstreaming attempts.

@LilyWangLL LilyWangLL added the category:port-update The issue is with a library, which is requesting update new revision label Nov 14, 2024
Copy link
Contributor Author

@donny-dont donny-dont left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok will make the changes tomorrow. Thanks for the review!

Removes `0002-suppress-msvc-warnings.patch`. The warnings were fixed and upstreamed into a downloaded patch. The spectre mitigation flags should be added in a triplet file.
@donny-dont
Copy link
Contributor Author

Okay @dg0yt and @LilyWangLL think this is ready to go

Copy link
Contributor

@dg0yt dg0yt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No more patching for warnings which are never looked at if not an upstream dev. 👍

Comment on lines -1 to -15
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 2f0dfa0..594c56f 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -136,6 +136,10 @@ if(WIN32)
endif()
set(PLATFORM_LIBS ${PLATFORM_LIBS} ws2_32 ntdll bcrypt)
endif()
+if(MSVC AND MSVC_VERSION GREATER_EQUAL 1912)
+ message(STATUS "Setting /Qspectre switch")
+ set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} /Qspectre")
+endif()

if(MSVC)
add_definitions(-Dinline=__inline)
Copy link
Contributor

@dg0yt dg0yt Nov 15, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do note that the port would no longer unconditionally enable spectre mitigation for newer MSVC. (This implements what I said about the new feature. I highlight the change because it was hidden in a patch with a different topic.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-update The issue is with a library, which is requesting update new revision
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants