Le 14/06/2013 15:19, Timo Juhani Lindfors a écrit : >> This doesn't really help when trying to diagnose things, and even for >> successful >> builds it's valuable to have the complete build log, including the parts how >> the >> upstream build system is called from the Debian packaging. > > This is a useful goal. However, since fixing many different source > packages is a lot of work I recently explored some alternative > approaches. For example, with systemtap we can simply log all execve() > invocations complete with timing information and end up with fully > structured build logs. > > Here's example output from the proof of concept from a few years ago: > > http://lindi.iki.fi/lindi/structured-buildlogs/logs/hello-2.6-1_amd64.build
How do you do that exactly? Cheers, -- Stéphane -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52837b52.4030...@debian.org
