From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/openocd: fix build with libgpiod2
Date: Tue, 7 May 2024 09:12:35 +0200 [thread overview]
Message-ID: <20240507091235.613acaaa@windsurf> (raw)
In-Reply-To: <20240506205250.1264901-1-fontaine.fabrice@gmail.com>
On Mon, 6 May 2024 22:52:49 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> openocd is not compatible with libgpiod2 resulting in the following
> build failure since the addition of libgpiod2 in commit
> 57391fad2e619395340b81957ddceab1b1df2e20:
>
> src/jtag/drivers/linuxgpiod.c: In function 'helper_get_line':
> src/jtag/drivers/linuxgpiod.c:283:19: error: 'GPIOD_LINE_REQUEST_DIRECTION_INPUT' undeclared (first use in this function); did you mean 'GPIOD_LINE_DIRECTION_INPUT'?
> 283 | int dir = GPIOD_LINE_REQUEST_DIRECTION_INPUT, flags = 0, val = 0, retval;
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> | GPIOD_LINE_DIRECTION_INPUT
>
> Fixes: 57391fad2e619395340b81957ddceab1b1df2e20
> - http://autobuild.buildroot.org/results/7195e8b76350f26ab3b963702d88b254512e6928
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/openocd/openocd.mk | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-05-07 7:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 20:52 [Buildroot] [PATCH 1/1] package/openocd: fix build with libgpiod2 Fabrice Fontaine
2024-05-07 7:12 ` Thomas Petazzoni via buildroot [this message]
2024-05-27 14:43 ` Peter Korsgaard
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=20240507091235.613acaaa@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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