Description of problem: /usr/lib64/pkgconfig/m4ri.pc contains %optflags in cflags. Packages are not supposed to add %optflags to *.pcs. Version-Release number of selected component (if applicable): m4ri-devel-20140914-1.fc22 Steps to Reproduce: 1. Check the m4ri-devel rpm's contents Actual results: ... Cflags: -I${includedir}/m4ri -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -mmmx -msse -msse2 -fopenmp ... Additional info: - I haven't checked other fedora releases, but I assume this issue to be present there, too. - The *.pc also should not add -mmmx -msse -msse2 to its *.pc. Actually it should not use these when building at all.
m4rie-20140914-2.fc22,m4ri-20140914-3.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/m4rie-20140914-2.fc22,m4ri-20140914-3.fc22
Package m4ri-20140914-3.fc22, m4rie-20140914-2.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing m4ri-20140914-3.fc22 m4rie-20140914-2.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-3429/m4rie-20140914-2.fc22,m4ri-20140914-3.fc22 then log in and leave karma (feedback).
m4ri-20140914-3.fc22, m4rie-20140914-2.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.