commit: 745e649426e2a012146ec5058817d02c30730937 Author: Mike Frysinger <vapier <AT> gentoo <DOT> org> AuthorDate: Fri Jan 20 22:28:01 2023 +0000 Commit: Mike Frysinger <vapier <AT> gentoo <DOT> org> CommitDate: Fri Jan 20 22:29:34 2023 +0000 URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=745e6494
sys-libs/newlib: drop -U_FORTIFY_SOURCE workaround The latest versions of newlib seem to build fine with this turned on, so drop the hack to see if there are any latent issues to fix upstream. Bug: https://bugs.gentoo.org/656018 Signed-off-by: Mike Frysinger <vapier <AT> gentoo.org> sys-libs/newlib/newlib-9999.ebuild | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/sys-libs/newlib/newlib-9999.ebuild b/sys-libs/newlib/newlib-9999.ebuild index 3b956c480a08..83237271fd55 100644 --- a/sys-libs/newlib/newlib-9999.ebuild +++ b/sys-libs/newlib/newlib-9999.ebuild @@ -37,12 +37,8 @@ NEWLIBBUILD="${WORKDIR}/build" NEWLIBNANOBUILD="${WORKDIR}/build.nano" NEWLIBNANOTMPINSTALL="${WORKDIR}/nano_tmp_install" -# Adding -U_FORTIFY_SOURCE to counter the effect of Gentoo's -# auto-addition of _FORTIFY_SOURCE at gcc site: bug #656018#c4 -# Currently newlib can't be built itself when _FORTIFY_SOURCE -# is set. -CFLAGS_FULL="-ffunction-sections -fdata-sections -U_FORTIFY_SOURCE" -CFLAGS_NANO="-Os -ffunction-sections -fdata-sections -U_FORTIFY_SOURCE" +CFLAGS_FULL="-ffunction-sections -fdata-sections" +CFLAGS_NANO="-Os -ffunction-sections -fdata-sections" pkg_setup() { # Reject newlib-on-glibc type installs
