Open tjaalton opened 6 months ago
An alternative solution would be to make IGC/CMakeLists.txt aware of the presence of D_FORTIFY_SOURCE in the environment and skip defining it again (or in case you strongly want to set the value of _FORTIFY_SOURCE to 2 for some reasons, undefine it first with -U as @tjaalton proposed)
An alternative solution would be to make IGC/CMakeLists.txt aware of the presence of D_FORTIFY_SOURCE in the environment and skip defining it again (or in case you strongly want to set the value of _FORTIFY_SOURCE to 2 for some reasons, undefine it first with -U as @tjaalton proposed)
@pszymich Ubuntu updating its FORTIFY_SOURCE
value of 2 in 22.04, to 3 in 24.04: https://ubuntu.com/blog/whats-new-in-security-for-ubuntu-24-04-lts
Is not the only distro doing such change. Fedora did similar change in 38: https://fedoraproject.org/wiki/Changes/Add_FORTIFY_SOURCE%3D3_to_distribution_build_flags
So that change is going to eventually propagate to RHEL too...
so please add -U_FORTIFY_SOURCE before defining it in IGC/CMakeLists.txt