From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-12-27
Date: Sat, 28 Dec 2013 13:02:04 +0100 [thread overview]
Message-ID: <20131228130204.3c2e9356@skate> (raw)
In-Reply-To: <20131228115043.GB3373@free.fr>
Dear Yann E. MORIN,
On Sat, 28 Dec 2013 12:50:43 +0100, Yann E. MORIN wrote:
> On 2013-12-28 12:42 +0100, Thomas Petazzoni spake thusly:
> > On Sat, 28 Dec 2013 11:26:10 +0100, Yann E. MORIN wrote:
> > > On 2013-12-28 08:30 +0100, Thomas Petazzoni spake thusly:
> > > > Detail of failures
> > > > powerpc | dvb-apps-be76da69f250 | NOK | http://autobuild.buildroot.net/results/c21fdc2b4e6564e4d557380e5e86aba0d78f1364/
> > >
> > > Too old kernel headers, should be fixed by an exception on the
> > > autobuilders.
> > I added the exception to the autobuilders yesterday.
>
> Ok, thanks! Ditto for tvheadend?
Yes.
> > > > powerpc | libevdev-0.5 | NOK | http://autobuild.buildroot.net/results/1f5c0689ae129ae5fa30f31a4f47ccbd7705ff00/
> > > > powerpc | libevdev-0.5 | NOK | http://autobuild.buildroot.net/results/1729043d9c977a59a4fdd7ccd3d16cfc8aef7678/
> > > > powerpc | libevdev-0.5 | NOK | http://autobuild.buildroot.net/results/3ab080e96576e0012fea853009811247338e665e/
> > >
> > > Can not find python-argparse. I'll check this.
> >
> > Maybe just disable Python support in libevdev or something like that.
>
> Since python is a mandatory dependency, I guess Peter and you must be
> using quite an old distribution on your autobuilders, since argparse is
> built-in on Python 2.7 and above.
Yes, the distros we're using are generally quite old.
> But I'll see if we can disable python support in libevdev, or make it
> depend on {host-,}python as needed.
The Python stuff is used to generate a header file. One solution is to
simply add a patch that contains the pre-generated version of this
header file. But well, maybe depending on host-python is easier and
more future-proof.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2013-12-28 12:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-28 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2013-12-27 Thomas Petazzoni
2013-12-28 10:26 ` Yann E. MORIN
2013-12-28 11:42 ` Thomas Petazzoni
2013-12-28 11:50 ` Yann E. MORIN
2013-12-28 12:02 ` Thomas Petazzoni [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131228130204.3c2e9356@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox