I have a failure in %configure which only happens on i686: https://koji.fedoraproject.org/koji/buildinfo?buildID=2710279
> configure: error: C compiler cannot create executables > See 'config.log' for more details This isn't about this specific failure, but more of a shell / RPM macro expansion question. How I can get config.log to be reliably, automatically printed on failure? I tried several variations of: %configure || { cat config.log; exit 1 } %configure \ || { cat config.log; exit 1 } if ! %configure; then cat config.log exit 1 fi if ! { %configure }; then cat config.log exit 1 fi None of them work in this case, and I don't understand exactly why. (Strangely other spec files use one of the above variations and apparently it works fine for them ...) A corollary to this question: Can't we have the %configure macro always dump config.log on failure? Another question: Does RPM always use bash as the shell? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com nbdkit - Flexible, fast NBD server with plugins https://gitlab.com/nbdkit/nbdkit -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue