On Sunday, February 27, 2011 19:41:50 Hans Verkuil wrote: > This message is generated daily by a cron job that builds v4l-dvb for > the kernels and architectures in the list below. > > Results of the daily build of v4l-dvb: > > date: Sun Feb 27 19:00:40 CET 2011 > git master: 1b59be2a6cdcb5a12e18d8315c07c94a624de48f > git media-master: gcc version: i686-linux-gcc (GCC) 4.5.1 > host hardware: x86_64 > host os: 2.6.32.5 > > linux-git-armv5: WARNINGS > linux-git-armv5-davinci: WARNINGS > linux-git-armv5-ixp: WARNINGS > linux-git-armv5-omap2: WARNINGS > linux-git-i686: WARNINGS > linux-git-m32r: WARNINGS > linux-git-mips: WARNINGS > linux-git-powerpc64: WARNINGS > linux-git-x86_64: WARNINGS > linux-2.6.31.12-i686: ERRORS > linux-2.6.32.6-i686: ERRORS > linux-2.6.33-i686: ERRORS > linux-2.6.34-i686: ERRORS > linux-2.6.35.3-i686: ERRORS > linux-2.6.36-i686: ERRORS > linux-2.6.37-i686: ERRORS > linux-2.6.31.12-x86_64: ERRORS > linux-2.6.32.6-x86_64: ERRORS > linux-2.6.33-x86_64: ERRORS > linux-2.6.34-x86_64: ERRORS > linux-2.6.35.3-x86_64: ERRORS > linux-2.6.36-x86_64: ERRORS > linux-2.6.37-x86_64: ERRORS > spec-git: OK > sparse: ERRORS Lots of errors here, but I wait with fixing this until the media controller patches are in. I prefer to go through this only once rather than after each new patch set that breaks the build given the limited amount of time that I have. Regards, Hans > > Detailed results are available here: > > http://www.xs4all.nl/~hverkuil/logs/Sunday.log > > Full logs are available here: > > http://www.xs4all.nl/~hverkuil/logs/Sunday.tar.bz2 > > The V4L-DVB specification from this daily build is here: > > http://www.xs4all.nl/~hverkuil/spec/media.html > -- > To unsubscribe from this list: send the line "unsubscribe linux-media" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- Hans Verkuil - video4linux developer - sponsored by Cisco -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
