From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15700] New: ./include/mount-api-utils.h:11:10: fatal error: linux/mount.h: No such file
Date: Tue, 18 Jul 2023 13:59:16 +0000 [thread overview]
Message-ID: <bug-15700-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15700
Bug ID: 15700
Summary: ./include/mount-api-utils.h:11:10: fatal error:
linux/mount.h: No such file
Product: buildroot
Version: 2023.05.1
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: glscene2010@gmail.com
CC: buildroot@uclibc.org
Target Milestone: ---
Created attachment 9625
--> https://bugs.busybox.net/attachment.cgi?id=9625&action=edit
Buildroot with util-linux config examples and logs
In my .config file I use
BR2_PACKAGE_UTIL_LINUX=y
because of it I have build fail on old kernels (4.19.269; 5.4.179). On kernel
5.10.19 and 6.1.26 works ok.
Looks like old kernel should use old util-linux (more old then v2.39)?
Steps to Reproduce:
git clone https://git.buildroot.net/buildroot && cd buildroot
[Put my files to buildroot/configs/]
make clean
make pc_x86_bios_defconfig_4_19_269
make
Build Date & Hardware
I use last buildroot from git (a89a632833dca00beb7443ef540571b281703ae1).
18 Jul 2023. Ubuntu 22 5.19.0-46-generic
See my config files and corresponding logs.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-07-18 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 13:59 bugzilla [this message]
2024-06-15 15:11 ` [Buildroot] [Bug 15700] ./include/mount-api-utils.h:11:10: fatal error: linux/mount.h: No such file bugzilla
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=bug-15700-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.