Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Brandon Maier via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Cc: Kalpesh Panchal <kalpesh.panchal2@collins.com>,
	Brandon Maier <brandon.maier@collins.com>
Subject: [Buildroot] [PATCH 1/1] aufs-util: fix build error for missing linux header
Date: Tue, 31 Oct 2023 23:03:36 +0000	[thread overview]
Message-ID: <20231031230336.51110-1-brandon.maier@collins.com> (raw)

From: Kalpesh Panchal <kalpesh.panchal2@collins.com>

added missing linux header path to fix below build error:

- $(LINUX_DIR)/include/uapi/linux/stddef.h:5:10:fatal error: linux/compiler_types.h: No such file or directory

Signed-off-by: Kalpesh Panchal <kalpesh.panchal2@collins.com>
Signed-off-by: Brandon Maier <brandon.maier@collins.com>
---
 package/aufs-util/aufs-util.mk | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/package/aufs-util/aufs-util.mk b/package/aufs-util/aufs-util.mk
index 32f3bca151..c334b8c014 100644
--- a/package/aufs-util/aufs-util.mk
+++ b/package/aufs-util/aufs-util.mk
@@ -21,11 +21,13 @@ AUFS_UTIL_DEPENDENCIES = linux
 AUFS_UTIL_HOST_CPPFLAGS = \
 	$(HOST_CPPFLAGS) \
 	-I$(LINUX_DIR)/include/uapi \
+	-I$(LINUX_DIR)/include \
 	-D__user=
 
 AUFS_UTIL_CPPFLAGS = \
 	$(TARGET_CPPFLAGS) \
 	-I$(LINUX_DIR)/include/uapi \
+	-I$(LINUX_DIR)/include \
 	-D__user=
 
 # rdu64 is supposed to provide the LFS variant of readdir(),
-- 
2.41.0

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2023-10-31 23:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31 23:03 Brandon Maier via buildroot [this message]
2024-10-26 16:46 ` [Buildroot] [PATCH 1/1] aufs-util: fix build error for missing linux header 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=20231031230336.51110-1-brandon.maier@collins.com \
    --to=buildroot@buildroot.org \
    --cc=brandon.maier@collins.com \
    --cc=kalpesh.panchal2@collins.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