Description of problem: There are the following C(XX)FLAGS definitions in the gperftools.spec: CFLAGS=`echo $RPM_OPT_FLAGS -fno-strict-aliasing -Wno-unused-local-typedefs -DTCMALLOC_LARGE_PAGES | sed -e 's/-Wp,-D_FORTIFY_SOURCE=2//g' | sed -e 's|-fexceptions||g'` CXXFLAGS=`echo $RPM_OPT_FLAGS -fno-strict-aliasing -Wno-unused-local-typedefs -DTCMALLOC_LARGE_PAGES | sed -e 's/-Wp,-D_FORTIFY_SOURCE=2//g' | sed -e 's|-fexceptions||g'` I don't have a clue why the FORTIFY_SOURCE is removed here and don't see it in other RPM packages (openSUSE nor upstream's). Thus, I think it is not necessary and gperftools should be built with FORTIFY_SOURCE. If there was a reason to do so, it should be tracked in some BZ (which I haven't found) or in a comment in spec file. Version-Release number of selected component (if applicable): gperftools-2.1-2.fc20.x86_64 Steps to Reproduce: 1. see the gperftools.spec Actual results: FORTIFY_SOURCE is disabled, explicitly removed from C(XX)FLAGS Expected results: FORTIFY_SOURCE is enabled, not removed from C(XX)FLAGS
I don't remember why I did that. Probably needed it to get a previous revision to build at some point. Confirmed that it is no longer necessary, re-enabling it in f20+.
gperftools-2.1-4.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/gperftools-2.1-4.fc20
Package gperftools-2.1-4.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gperftools-2.1-4.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-0303/gperftools-2.1-4.fc20 then log in and leave karma (feedback).
gperftools-2.1-4.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.