Allow building with WOLFSSL_NO_MALLOC again #8053
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
retest this please |
danielinux
force-pushed
the
fix-no-malloc
branch
from
e70556c to
a3f6bab
Compare
|
retest this please |
douzzer
approved these changes
Oct 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
A few malloc calls added since the last release are preventing simple builds with nostdlib, e.g. using WOLFCRYPT_ONLY and WOLFSSL_NO_MALLOC.
Testing
Spotted while updating submodules in wolfboot:
https://github.com/wolfSSL/wolfBoot/actions/runs/11247180283/job/31270223935?pr=507