From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14836] New: aufs-util build not working
Date: Sun, 05 Jun 2022 14:07:17 +0000 [thread overview]
Message-ID: <bug-14836-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=14836
Bug ID: 14836
Summary: aufs-util build not working
Product: buildroot
Version: 2022.02.2
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: me@blob.dev
CC: buildroot@uclibc.org
Target Milestone: ---
Hello
We have observed a build failure related to aufs-util (version aufs5.8) on
buildroot 2022.02.2 and 2022.05-rc2. Attempts at fixing the problem ourselves
were unsuccessful, since the errors just kept on coming. You fix one, another
pops up. The first error:
```
In file included from
/root/test2/buildroot-2022.02.2/output/build/linux-5.15.18/include/uapi/linux/posix_types.h:5,
from
/root/test2/buildroot-2022.02.2/output/build/linux-5.15.18/include/uapi/linux/types.h:14,
from
/root/test2/buildroot-2022.02.2/output/build/linux-5.15.18/include/uapi/linux/stat.h:5,
from /usr/include/x86_64-linux-gnu/bits/statx.h:31,
from /usr/include/x86_64-linux-gnu/sys/stat.h:446,
from /usr/include/ftw.h:28,
from au_util.h:23,
from ver.c:25:
/root/test2/buildroot-2022.02.2/output/build/linux-5.15.18/include/uapi/linux/stddef.h:2:10:
fatal error: linux/compiler_types.h: No such file or directory
2 | #include <linux/compiler_types.h>
| ^~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
```
We fixed this by modifying the include paths, but then the second error came:
```
gcc: error: pre: No such file or directory
make[1]: *** [<builtin>: c2sh] Error 1
```
This was fixed by creating an empty file called pre in the aufs-util build
directory, but then, we got this error instead:
```
make[2]: *** No rule to make target '../extlib/glibc/error_at_line.h', needed
by 'libau.o'. Stop.
make[2]: Leaving directory
'/root/test/buildroot-2022.05-rc2/output/build/aufs-util-aufs5.8/libau'
make[1]: *** [Makefile:106: all] Error 2
```
At this point we gave up trying to fix this ourselves.
Regards
--
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:[~2022-06-05 14:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-05 14:07 bugzilla [this message]
2024-06-15 15:03 ` [Buildroot] [Bug 14836] aufs-util build not working 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-14836-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox