Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/mtd: update lib{mtd, ubi}.h path
Date: Sun, 18 Jul 2021 14:00:58 +0200	[thread overview]
Message-ID: <20210718140058.47ac4d31@windsurf> (raw)
In-Reply-To: <20210718083412.1904311-1-fontaine.fabrice@gmail.com>

On Sun, 18 Jul 2021 10:34:12 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> Update lib{mtd,ubi}.h path to fix the following build failure raised
> since bump of swupdate to version 2021.04 in commit
> 2c6b0359c3b819fadb4437b2d780e95c32fdab21:
> 
> In file included from corelib/mtd-interface.c:21:
> include/flash.h:13:10: fatal error: libmtd.h: No such file or directory
>    13 | #include <libmtd.h>
>       |          ^~~~~~~~~~
> 
> This build failure is raised because of
> https://github.com/sbabic/swupdate/commit/0c672866d4a9fe8f0808b5d8a0afb95c13c4c138
> 
> Fixes:
>  - http://autobuild.buildroot.org/results/d475bdb341d2afecf12e404dfa093e58221b9882
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  package/mtd/mtd.mk | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

Isn't there a chance for this to break other packages? Is it just
swupdate that is using the MTD headers?

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

  reply	other threads:[~2021-07-18 12:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-18  8:34 [Buildroot] [PATCH 1/1] package/mtd: update lib{mtd,ubi}.h path Fabrice Fontaine
2021-07-18 12:00 ` Thomas Petazzoni [this message]
2021-07-18 12:51   ` [Buildroot] [PATCH 1/1] package/mtd: update lib{mtd, ubi}.h path Yann E. MORIN
2021-07-25 16:18     ` Arnout Vandecappelle

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=20210718140058.47ac4d31@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox