[oe] tinderbox, bug reports and a freshly-broken mplayer

[Robert P. J. Day]

  in order to keep the peace, i'm more than willing to file actual OE
bug reports for breakage i discover when building.  specifically, i'm
almost always trying to build beagleboard-demo-image on my up-to-date
fedora system, which seems to be a relatively unpopular working system
for most people here (except for philip b.), so i'm getting used to
running into breakage that no one else is seeing -- it's just a fact
of life.

  ignoring gnome-games for now, after a recent "git pull" on the OE
dev branch, the "mplayer" package now no longer builds.  from the git
log, i can see:

=====

commit 33c882b663a1dd229d0ebcb187648838d0164795
Author: Koen Kooi <koen at openembedded.org>
Date:   Sun Jan 17 14:52:44 2010 +0100

    mplayer: bump SRCREV for some more ARM fixes

diff --git a/recipes/mplayer/mplayer_svn.bb
b/recipes/mplayer/mplayer_svn.bb
index 58a4bc7..d3fc2f7 100644
--- a/recipes/mplayer/mplayer_svn.bb
+++ b/recipes/mplayer/mplayer_svn.bb
@@ -15,7 +15,7 @@ SRC_URI =
"svn://svn.mplayerhq.hu/mplayer;module=trunk \
           file://fix-addrinfo.patch;patch=1;maxrev=30302 \
 "

-SRCREV = "30247"
+SRCREV = "30345"
 SRC_URI_append_armv7a = " \
                file://omapfb.patch;patch=1 \
           file://vo_omapfb.c \

=====

  if i "git reset" to the commit just before that, it builds fine;
ergo, that seems to be the commit that broke it.  a wild guess is that
the "maxrev" parameters are the cause, given that at least one now
falls below the requested svn revision, causing an essential patch to
no longer be applied, but that's just a guess until i look more
closely.

  the tail end of the log file:

fmt-conversion.c
fmt-conversion.c:28: error: 'PIX_FMT_RGB32' undeclared here (not in a function)
fmt-conversion.c:30: error: 'PIX_FMT_RGB565' undeclared here (not in a function)
fmt-conversion.c:31: error: 'PIX_FMT_RGB555' undeclared here (not in a function)
fmt-conversion.c:40: error: 'PIX_FMT_BGR32' undeclared here (not in a function)
fmt-conversion.c:42: error: 'PIX_FMT_BGR565' undeclared here (not in a function)
fmt-conversion.c:43: error: 'PIX_FMT_BGR555' undeclared here (not in a function)
make: *** [fmt-conversion.o] Error 1
FATAL: oe_runmake failed


  so ... i can file this over at http://bugs.openembedded.net/ if
that's the way to go.  but others were talking about this tinderbox
thing, which i've never used.  a quick glance suggests it's a more
formal, automated way of doing regular builds.  would that be
appropriate for me, if it's understood i'm always building on the same
distro?  feel free to point me at a quick intro, or i'll just file a
regular bug if that's the way to go.

rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================