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
_FORTIFY_SOURCE redefined while compiling on Gentoo with Portage #631
Comments
I guess it is slightly odd to unconditionally set _FORTIFY_SOURCE -- @superm1 any ideas here? My gut instinct is just to remove it from the |
|
I don't think that'll work; it's not really a flag it's just a #define. I'll remove it. |
hughsie
added a commit
that referenced
this issue
Aug 8, 2018
hughsie
added a commit
that referenced
this issue
Aug 8, 2018
superm1
pushed a commit
to fwupd/fwupd-efi
that referenced
this issue
Apr 19, 2021
superm1
pushed a commit
to fwupd/fwupd-efi
that referenced
this issue
Apr 21, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's a problem with compiling.
Please answer the following questions:
from source
,pacman
,apt-get
, etc): PortageThe compiling failed on Gentoo at:
The problem seems to be Gentoo's GCC has built-in parameter that sets
-D_FORTIFY_SOURCE
to another value, and the build system set that value again.My solution is to add
-U_FORTIFY_SOURCE
before-D_FORTIFY_SOURCE=2
.I believe there will be better solution so I opened this issue.
Link to Gentoo Bugzilla: https://bugs.gentoo.org/661068
The text was updated successfully, but these errors were encountered: