Created attachment 856248 [details] Patch provided by ville.skytta Don't discard user CFLAGS, append to them instead Package is not built with $RPM_OPT_FLAGS. Fix attached, please apply upstream as well. Honoring proper Fedora CFLAGS causes a build failure due to -Werror being used so additional fixing will be required: [...]/server_test.c: In function 'ufd_handler': [...]/server_test.c:99:18: error: ignoring return value of 'write', declared with attribute warn_unused_result [-Werror=unused-result] write(fd[1], "X", 1);
qpid-dispatch-0.1-3.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/qpid-dispatch-0.1-3.fc20
qpid-dispatch-0.1-3.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/qpid-dispatch-0.1-3.fc19
qpid-dispatch-0.1-3.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/qpid-dispatch-0.1-3.el6
Package qpid-dispatch-0.1-3.el6: * should fix your issue, * was pushed to the Fedora EPEL 6 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing qpid-dispatch-0.1-3.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-0422/qpid-dispatch-0.1-3.el6 then log in and leave karma (feedback).
qpid-dispatch-0.1-4.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/qpid-dispatch-0.1-4.fc20
qpid-dispatch-0.1-4.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/qpid-dispatch-0.1-4.fc19
qpid-dispatch-0.1-4.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
qpid-dispatch-0.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.
qpid-dispatch-0.1-3.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.