Skip to content

Conversation

@bagder
Copy link
Member

@bagder bagder commented Feb 6, 2025

The previous runtime check using strcmp() risks failing when zlib reaches 1.10. While this instead changes the logic to a cruder build-time instead of runtime, it avoids the 1.10 risk.

I verified that ZLIB_VERNUM has been provided since at least the 1.2.0.3 release.

1.2.0.4 was released on 10 August 2003.

Reported-by: Fay Stegerman

The previous runtime check using strcmp() risks failing when zlib
reaches 1.10. While this instead changes the logic to a cruder
build-time instead of runtime, it avoids the 1.10 risk.

I verified that ZLIB_VERNUM has been provide since at least the 1.2.0.3
release.

Reported-by: Fay Stegerman
@bagder bagder closed this in 34acdf9 Feb 6, 2025
@bagder bagder deleted the bagder/zlib-version-check branch February 6, 2025 09:27
pps83 pushed a commit to pps83/curl that referenced this pull request Apr 26, 2025
The previous runtime check using strcmp() risks failing when zlib
reaches 1.10. While this instead changes the logic to a cruder
build-time instead of runtime, it avoids the 1.10 risk.

I verified that ZLIB_VERNUM has been provided since at least the 1.2.0.3
release.

1.2.0.4 was released on 10 August 2003.

Reported-by: Fay Stegerman
Closes curl#16202
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant