I guess hornetq 2.4.0-3's native bits are not being built with $RPM_OPT_FLAGS. Guess, because the build doesn't log the c++ compiler flags it uses, doesn't seem anything would use $RPM_OPT_FLAGS or other envifonment variables, and that -debuginfo contains no sources.
I'll disable the debuginfo package since it does not make sense when using the nar maven plugin. But I need to wait for the qpid-proton-java package to become available since it was dropped from qpid-proton main package.
Aren't the generated executables/shared libraries/objects ordinary ones? If yes, they should be built with $RPM_OPT_FLAGS being honored, no matter what builds them. http://fedoraproject.org/wiki/Packaging:Guidelines#Compiler_flags
(In reply to Ville Skyttä from comment #2) > Aren't the generated executables/shared libraries/objects ordinary ones? If > yes, they should be built with $RPM_OPT_FLAGS being honored, no matter what > builds them. > > http://fedoraproject.org/wiki/Packaging:Guidelines#Compiler_flags This is an issue in nar-maven-plugin then, I opened bug 1056049.
hornetq-2.4.0-4.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/hornetq-2.4.0-4.fc20
hornetq-2.4.0-4.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.