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] Your build results for 2017-07-01
Date: Sun, 2 Jul 2017 23:38:11 +0200	[thread overview]
Message-ID: <20170702233811.226f8789@windsurf> (raw)
In-Reply-To: <CAAkeqgV9VY0CEZAxPuQJ_vSBFudcWWwRHzra62tn=98B8HhMhA@mail.gmail.com>

Hello,

On Sun, 2 Jul 2017 12:57:14 -0700, Andrey Yurovsky wrote:
> On Sat, Jul 1, 2017 at 11:31 PM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
> > Hello,
> >
> > This is the list of Buildroot build failures that occured on
> > 2017-07-01, and for which you are a registered architecture developer
> > or package developer. Please help us improving the quality of
> > Buildroot by investigating those build failures and sending patches to
> > fix them. Thanks!
> >
> > Build failures related to your packages:
> >
> >          sh4 |                host-rauc-0.1.1 | http://autobuild.buildroot.net/results/2695202ee3b0734430abc2db03828a45cd5e5ef5
> >         m68k |                host-rauc-0.1.1 | http://autobuild.buildroot.net/results/77a5db1120bf90ccaac00cfc0a8db358cacd894c  
> 
> These are failing because openssl and libglib2 aren't available (for
> the host). I'm not sure why the others didn't fail, perhaps the
> environment for them does provide these. We don't have host recipes
> for either one so perhaps buildroot shouldn't provide host-rauc after
> all? Or is there a way to indicate that these are external
> dependencies for this host tool? Or otherwise should buildroot try to
> provide host builds of openssl and glib2?

In such cases, we obviously add dependencies on host-openssl and
host-libglib2, both of which already exist. I've therefore pushed a
commit that fixes those build issues:

  https://github.com/buildroot/buildroot/commit/8c7966d22e53ac83f2d8fe41b1a04c3f598502f4
  (our gitweb is down, so pointing to our github.com repo)

Thanks for investigating this issue in the first place!

Best regards,

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

      reply	other threads:[~2017-07-02 21:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170702063107.D1E2621E01@mail.free-electrons.com>
2017-07-02 19:57 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2017-07-01 Andrey Yurovsky
2017-07-02 21:38   ` 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=20170702233811.226f8789@windsurf \
    --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