bypass _FORTIFY_SOURCE=3 #33
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
mdavidsaver
force-pushed
the
bypass-fortify
branch
from
2147e39 to
1950c4a
Compare
mdavidsaver
force-pushed
the
bypass-fortify
branch
from
1950c4a to
fa8ec32
Compare
|
Merged. This is a workaround which will be removed with the next merge from epics-base. |
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.
Attempt to address #32 as described by epics-base/epics-base#514 (comment) by redefining
_FORTIFY_SOURCE=3to_FORTIFY_SOURCE=2. This should only be attempted if_FORTIFY_SOURCEis predefined.