On Fri, Feb 06, 2015 at 10:41:51AM +0000, David Howells wrote:
> Can rpmbuild be taught to produce a 'build logs' rpm (or tarball or something)
> that isn't automatically added to the installation set by koji/bodhi and that
> can get generated even in the event of a build failure?
>
> I have seen two examples of where this could be useful:
>
> (1) gcc-5 dumps a whole chunk of tar'd, bzip'd and uuencoded testing logs to
> stdout because it has nowhere else to put them.
>
> (2) I'm seeing a config failure building cross-gcc on ARM that doesn't occur
> on x86_64 or i686 - but it happens in koji where I can't get at the
> config.log to see what happened.
I don't think an RPM would help. However it would be nice if Koji
allowed you to pull files from the build tree, especially after a
failure.
In the past I have done this:
%{configure} || { cat config.log ; exit 1 }
I also did some hairy uuencoding to dump out binaries that I wanted to
capture.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages. http://libguestfs.org
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
