On 08/05/2018 01:13 PM, Florian Weimer wrote:
On 08/05/2018 09:48 PM, Samuel Sieb wrote:
What am I missing here? Why can't this be put in RPM macros? Then
when the situation changes in the future, there's only one place to
change.
There already is such a macro, %{valgrind_arches}, but it may not
accurately reflect the suitability of the run-time behavior of valgrind
on a particular architecture. For example, the undefinedness tracking
might not be sufficiently accurate for the testsuite of a specific
package, so running the testsuite under valgrind gives false positives.
So the original post is only to be used for specific exceptional cases?
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/VZIWOM3AHH66MAWIVFWNLHPSCFUTTDAF/
