-
Notifications
You must be signed in to change notification settings - Fork 103
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
Fix build of perl bindings without external _FORTIFY_SOURCE
define
#223
Conversation
Outside of fedora build infrastructure `_FORTIFY_SOURCE` is not defined but the perl bindings require it. We also have to handle different `_FORTIFY_SOURCE` definitions in rawhide vs stable fedoras.
LGTM |
Hm, locally in Fedora 36 container, I get "-D_FORTIFY_SOURCE defined but value is too low"... |
Interesting it seems to work for me:
Did I do something differently? |
Ok, I am sorry, I used an old dbox and I can't reproduce it elsewhere. Otherwise it looks good, so I am merging it. |
Hm, I still get this error on my fully updated Fedora 36:
It builds in the container, thougt. So I guess I need to investigate what the difference between my system and the container is. |
Oh my, sorry. I really thought it must have been something only in the very old dbox container and didn't want to block this on it. I'll keep looking into it as well then. |
Looks like it's a ccache problem - https://bugzilla.redhat.com/show_bug.cgi?id=2160275 |
Thank you, Marek! |
Just ran into the build failure on F36. Okay, cleared up by ccache --clean, but... This weird dance around a distro and distro-version specific compiler setting seems a bit much. I think it's best for upstreams to stay away from this stuff to a large degree, distros will want to override your flags anyhow and the more you have flags by default the more likely weird conflicts become. |
Outside of fedora build infrastructure
_FORTIFY_SOURCE
is not defined but the perl bindings require it.