From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11536] New: dt-utils building fails with glibc 2.28
Date: Sun, 02 Dec 2018 14:51:21 +0000 [thread overview]
Message-ID: <bug-11536-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11536
Bug ID: 11536
Summary: dt-utils building fails with glibc 2.28
Product: buildroot
Version: 2018.11
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: pvizeli at syshack.ch
CC: buildroot at uclibc.org
Target Milestone: ---
>>> dt-utils v2018.05.0 Building
PATH="/build/buildroot/output/host/bin:/build/buildroot/output/host/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
/usr/bin/make -j9 -C /build/buildroot/output/build/dt-utils-v2018.05.0/
make[1]: Entering directory '/build/buildroot/output/build/dt-utils-v2018.05.0'
/usr/bin/make --no-print-directory all-am
GEN src/libdt-utils.pc
CC src/src_libdt_utils_la-crc32.lo
CC src/src_libdt_utils_la-libdt.lo
CC src/src_libdt_utils_la-fdt.lo
CC src/crypto/barebox_state-digest.o
CC src/crypto/barebox_state-hmac.o
CC src/crypto/barebox_state-sha1.o
CC src/crypto/barebox_state-sha2.o
CC src/barebox_state-keystore-blob.o
CC src/barebox_state-base64.o
In file included from src/crypto/digest.c:24:0:
../../host/x86_64-buildroot-linux-gnu/sysroot/usr/include/linux/stat.h:56:8:
error: redefinition of 'struct statx_timestamp'
struct statx_timestamp {
^~~~~~~~~~~~~~~
In file included from
../../host/x86_64-buildroot-linux-gnu/sysroot/usr/include/sys/stat.h:446:0,
from ./src/dt/common.h:15,
from src/crypto/digest.c:19:
../../host/x86_64-buildroot-linux-gnu/sysroot/usr/include/bits/statx.h:25:8:
note: originally defined here
struct statx_timestamp
^~~~~~~~~~~~~~~
In file included from src/crypto/digest.c:24:0:
../../host/x86_64-buildroot-linux-gnu/sysroot/usr/include/linux/stat.h:99:8:
error: redefinition of 'struct statx'
struct statx {
^~~~~
In file included from
../../host/x86_64-buildroot-linux-gnu/sysroot/usr/include/sys/stat.h:446:0,
from ./src/dt/common.h:15,
from src/crypto/digest.c:19:
../../host/x86_64-buildroot-linux-gnu/sysroot/usr/include/bits/statx.h:36:8:
note: originally defined here
struct statx
^~~~~
Makefile:809: recipe for target 'src/crypto/barebox_state-digest.o' failed
make[2]: *** [src/crypto/barebox_state-digest.o] Error 1
make[2]: *** Waiting for unfinished jobs....
Makefile:511: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/build/buildroot/output/build/dt-utils-v2018.05.0'
package/pkg-generic.mk:229: recipe for target
'/build/buildroot/output/build/dt-utils-v2018.05.0/.stamp_built' failed
make: *** [/build/buildroot/output/build/dt-utils-v2018.05.0/.stamp_built]
Error 2
make: Leaving directory '/build/buildroot'
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2018-12-02 14:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-02 14:51 bugzilla at busybox.net [this message]
2018-12-03 12:39 ` [Buildroot] [Bug 11536] dt-utils building fails with glibc 2.28 bugzilla at busybox.net
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-11536-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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