From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Brandon Maier via buildroot <buildroot@buildroot.org>
Cc: Brandon Maier <brandon.maier@collins.com>,
Kalpesh Panchal <kalpesh.panchal2@collins.com>
Subject: Re: [Buildroot] [PATCH 1/1] aufs-util: fix build error for missing linux header
Date: Sat, 26 Oct 2024 18:46:00 +0200 [thread overview]
Message-ID: <20241026184600.291039c3@windsurf> (raw)
In-Reply-To: <20231031230336.51110-1-brandon.maier@collins.com>
On Tue, 31 Oct 2023 23:03:36 +0000
Brandon Maier via buildroot <buildroot@buildroot.org> wrote:
> 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>
Could you document a bit more your commit log?
Which defconfig exhibits the issue?
Since when this problem started occurring?
We have no autobuilder issues for this, and you don't explain why this
used to work, but doesn't work anymore.
Could you do a bit more research, and provide a more
exhaustive/documented explanation?
Thanks a lot!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-10-26 16:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 23:03 [Buildroot] [PATCH 1/1] aufs-util: fix build error for missing linux header Brandon Maier via buildroot
2024-10-26 16:46 ` Thomas Petazzoni via buildroot [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=20241026184600.291039c3@windsurf \
--to=buildroot@buildroot.org \
--cc=brandon.maier@collins.com \
--cc=kalpesh.panchal2@collins.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