-
Notifications
You must be signed in to change notification settings - Fork 816
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
[Bug]: hardcoded _FORTIFY_SOURCE=2 conflicts with distribution presets #4697
Comments
@bnavigator I am curious why is this needed now ? |
we may still need to ensure that other community binary builds of desktop client are not done without a safe and proper use of |
Yes, openSUSE Tumbleweed changed their presets from https://lists.opensuse.org/archives/list/[email protected]/message/55RQGTWGCLN4GSIDEDIWMQTVZ7UNITYX/ |
That's why I only mention the patch as work around. We can use it in the distribution, because we know that we have even safer flags already specified. It's obviously not suited for builds where you would end up without any flag. |
Bug description
Uncovered by #4690, the compilation of the desktop client fails, because there are two (!) places in the cmake files where _FORTIFY_SOURCE=2 is hardcoded, but the next level _FORTIFY_SOURCE=3 is in the CFLAGS presets from the distribution.
See also https://bugzilla.opensuse.org/show_bug.cgi?id=1201070
Steps to reproduce
-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3
in theCFLAGS
Expected behavior
Which files are affected by this bug
src/CMakeLists.txt, make/modules/DefineCompilerFlags.cmake
Operating system
Linux
Which version of the operating system you are running.
openSUSE Tumbleweed 20220702
Package
Distro package manager
Nextcloud Server version
N/A
Nextcloud Desktop Client version
3.5.1
Is this bug present after an update or on a fresh install?
Fresh desktop client install
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
Are you using an external user-backend?
Nextcloud Server logs
Additional info
Failing build log:
Workaround:
The text was updated successfully, but these errors were encountered: