fix compiler error: "_FORTIFY_SOURCE" redefined #650
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
sgpires
reviewed
Mar 20, 2024
|
Sure. Just deside how to handle it. The project can deside. I only want to build it with buildroot without further patching to fix this double definition in new compiler versions. So what shall I implement? The option above? Just tell me. It only needs to compile. |
Co-authored-by: sgpires <[email protected]>
fcmonteiro
requested review from
sgpires and
goncaloalmeida
and removed request for
sgpires
sgpires
approved these changes
Mar 21, 2024
goncaloalmeida
approved these changes
Mar 21, 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.
Request to fix compiler error because new compilers (gcc >= 7.5.0-3ubuntu1~18.04) seems to define the macro _FORTIFY_SOURCE by default and creates a conflict with the macro definition from the project.
Details can be found in the issue here.