All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2018-08-23
Date: Fri, 24 Aug 2018 11:05:53 +0200	[thread overview]
Message-ID: <20180824110553.2121c1b2@windsurf> (raw)
In-Reply-To: <20180824075557.GL9365@scaer>

Hello,

On Fri, 24 Aug 2018 09:55:57 +0200, Yann E. MORIN wrote:

> On 2018-08-24 08:00 +0200, Thomas Petazzoni spake thusly:
> > Results for branch 'master'
> >         i586 |                  host-rauc-0.4 | NOK | http://autobuild.buildroot.net/results/7e1cbeb458cb6536a36eae0d24cefb36edb22f55 |     
> >       x86_64 |                  host-rauc-0.4 | NOK | http://autobuild.buildroot.net/results/1b32b5daf5d3e3cf77e6779af7d9b79ce7e6a8e5 |       
> 
> Those two occur on Hollis' autobuilder (again! ;-)), because the host
> has kernel headers v2.6.32, which are too old for rauc, which needs
> headers >= 3.0. However, we have no way to express this dependency on
> host headers, only for the target headers...
> 
> (patch incoming to add that dependency for the target variant).

Rather than adding a dependency on >= 3.0 kernel headers, perhaps we
can find a way to make the code not use the missing definitions when
they are not available. This would avoid the >= 3.0 dependency for the
target variant *and* solve the host build problem at the same time.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2018-08-24  9:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-24  6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-08-23 Thomas Petazzoni
2018-08-24  6:52 ` Gwenhael Goavec-Merou
2018-08-24  8:17   ` Yann E. MORIN
2018-08-24  8:51     ` Yann E. MORIN
2018-08-24  7:55 ` Yann E. MORIN
2018-08-24  9:05   ` 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=20180824110553.2121c1b2@windsurf \
    --to=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.