Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2016-03-03
Date: Fri, 4 Mar 2016 21:24:19 +0100	[thread overview]
Message-ID: <20160304212419.6529ec0c@free-electrons.com> (raw)
In-Reply-To: <CAAMH-ytHBRRC7A3aOynB6TVyJgr82dge8s1pMemreE4N_aXF5w@mail.gmail.com>

Gary,

On Fri, 4 Mar 2016 16:13:29 +0100, Gary Bisson wrote:

> > Classification of failures by reason
> > ====================================
> >
> >               host-libcap-2.24 | 22
> >      python-cryptography-1.2.2 | 22
> >            libimxvpuapi-0.10.1 | 5
> 
> I've looked at the libimxvpuapi failures and they are actually imx-vpu failures.
> 
> The latest imx-vpu only builds if the PLATFORM is MX27, MX53 or MX6Q
> but our default is MX25. So the imx-vpu package just does nothing and
> then libimxvpuapi fails during configuration because libvpu is
> missing.

Thanks for investigating!

> I'm looking into a solution but those FREESCALE_IMX_PLATFORM_* are not
> easy to play with.

What do you find not easy with those options?

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-03-04 20:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-04  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-03-03 Thomas Petazzoni
2016-03-04 15:13 ` Gary Bisson
2016-03-04 20:24   ` Thomas Petazzoni [this message]
2016-03-07 10:07     ` Gary Bisson
2016-03-08 21:59       ` Peter Korsgaard
2016-03-09 10:50         ` Gary Bisson

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=20160304212419.6529ec0c@free-electrons.com \
    --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