From: Alexander Egorenkov <egorenar-dev@posteo.net>
To: buildroot@buildroot.org
Cc: Alexander Egorenkov <egorenar-dev@posteo.net>
Subject: [Buildroot] [PATCH 1/1] package/multipath-tools: fix path to kernel headers
Date: Sat, 18 Feb 2023 09:29:43 +0000 [thread overview]
Message-ID: <20230218092943.2598-1-egorenar-dev@posteo.net> (raw)
With change 6b7d47be3b23 ("multipath-tools: Makefiles: simplify code for
include dirs") the Makefile variable 'LINUX_HEADERS_INCDIR' has been replaced
with 'kernel_incdir'.
fpin_handlers.c:355:32: note: each undeclared identifier is reported only once for each function it appears in
fpin_handlers.c:360:37: error: ‘ELS_DTAG_LNK_INTEGRITY’ undeclared (first use in this function)
360 | if (dtag == ELS_DTAG_LNK_INTEGRITY) {
| ^~~~~~~~~~~~~~~~~~~~~~
make[2]: *** [../Makefile.inc:116: fpin_handlers.o] Error 1
Fixes: http://autobuild.buildroot.net/results/e0f56ef924c13d6b1535fdc350ad8ecc06ea0a58
Signed-off-by: Alexander Egorenkov <egorenar-dev@posteo.net>
---
package/multipath-tools/multipath-tools.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/multipath-tools/multipath-tools.mk b/package/multipath-tools/multipath-tools.mk
index 90394fae9fde..23b3cc944267 100644
--- a/package/multipath-tools/multipath-tools.mk
+++ b/package/multipath-tools/multipath-tools.mk
@@ -22,7 +22,7 @@ MULTIPATH_TOOLS_CPE_ID_VENDOR = opensvc
MULTIPATH_TOOLS_DEPENDENCIES = lvm2 json-c readline udev liburcu libaio host-pkgconf
MULTIPATH_TOOLS_MAKE_OPTS = \
- LINUX_HEADERS_INCDIR=$(STAGING_DIR)/usr/include \
+ kernel_incdir=$(STAGING_DIR)/usr/include \
LIB="lib" \
RUN="run" \
OPTFLAGS="" \
--
2.39.2
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-02-18 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-18 9:29 Alexander Egorenkov [this message]
2023-02-21 8:37 ` [Buildroot] [PATCH 1/1] package/multipath-tools: fix path to kernel headers Thomas Petazzoni via buildroot
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=20230218092943.2598-1-egorenar-dev@posteo.net \
--to=egorenar-dev@posteo.net \
--cc=buildroot@buildroot.org \
/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