Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-12-27
Date: Sat, 28 Dec 2013 11:26:10 +0100	[thread overview]
Message-ID: <20131228102610.GA3373@free.fr> (raw)
In-Reply-To: <20131228073009.0C3D910103D@stock.ovh.net>

Thomas, All,

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.

>    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.

>    powerpc | make: *** [snmppp-legal-inf... | NOK | http://autobuild.buildroot.net/results/a1653834d24cecc5e3bd1aded78811b794126963/
>    powerpc | make: *** [snmppp-legal-inf... | NOK | http://autobuild.buildroot.net/results/c99120ec2f33d7d05dfb4b4a5338e0a4ce1d9d4c/
>        arm | make: *** [snmppp-legal-inf... | NOK | http://autobuild.buildroot.net/results/e64c3edcb00132620b07ad815c6e4d33b70c262f/

Should be fixed by:
    006e9d6: snmppp: fix legal informations after version bump

>     x86_64 |                     ola-0.8.32 | NOK | http://autobuild.buildroot.net/results/7c6aae3a50e50962db02b63306f47bee755b1b1f/
>     x86_64 |                     ola-0.8.32 | NOK | http://autobuild.buildroot.net/results/54deb02959e1c011c3971b23f409f47c285a88e4/
>    powerpc |                     ola-0.8.32 | NOK | http://autobuild.buildroot.net/results/4d3d5129fce43647f781223e223ca22cd348e1b5/

Still "can't find python-protobuf".

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2013-12-28 10:26 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 [this message]
2013-12-28 11:42   ` Thomas Petazzoni
2013-12-28 11:50     ` Yann E. MORIN
2013-12-28 12:02       ` Thomas Petazzoni

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=20131228102610.GA3373@free.fr \
    --to=yann.morin.1998@free.fr \
    --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