From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15721] New: fakeroot 1.32.1 fails to build on CentOS 7.x machines
Date: Fri, 11 Aug 2023 22:11:23 +0000 [thread overview]
Message-ID: <bug-15721-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15721
Bug ID: 15721
Summary: fakeroot 1.32.1 fails to build on CentOS 7.x machines
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: abrodkin@synopsys.com
CC: buildroot@uclibc.org
Target Milestone: ---
Starting from commit f1350977634f ("package/fakeroot: bump to version 1.32.1"),
see [1], Buildroot fails to compile early that way:
----------------------->8-----------------------
libtool: compile: /usr/bin/gcc -std=gnu11 -DHAVE_CONFIG_H -I.
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64
-I.../buildroot/fakeroot/output/host/include -O2
-I.../buildroot/fakeroot/output/host/include -c libfakeroot_time64.c -fPIC
-DPIC -o .libs/libfakeroot_time64_la-libfakeroot_time64.o
In file included from libfakeroot_time64.c:13:0:
/usr/include/fts.h:41:3: error: #error "<fts.h> cannot be used with
-D_FILE_OFFSET_BITS==64"
# error "<fts.h> cannot be used with -D_FILE_OFFSET_BITS==64"
^
make[3]: *** [libfakeroot_time64_la-libfakeroot_time64.lo] Error 1
make[3]: Leaving directory
`.../buildroot/fakeroot/output/build/host-fakeroot-1.32.1'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`.../buildroot/fakeroot/output/build/host-fakeroot-1.32.1'
make[1]: *** [all] Error 2
make[1]: Leaving directory
`.../buildroot/fakeroot/output/build/host-fakeroot-1.32.1'
----------------------->8-----------------------
That happens due to a change in the fakeroot, see [2].
It boils down to use of "fts.h" on 64-bit system with old glibc.
I.e. support of "fts.h" was added in glibc 2.23, see [3]. And in its turn
CentOS 7.x uses glibc 2.17, thus we see this (shamelessly copied from [4]):
----------------------->8-----------------------
> cat test.c
#include <fts.h>
int main() {
}
> cc -D_FILE_OFFSET_BITS=64 test.c
In file included from test.c:1:0:
/usr/include/fts.h:41:3: error: #error "<fts.h> cannot be used with
-D_FILE_OFFSET_BITS==64"
# error "<fts.h> cannot be used with -D_FILE_OFFSET_BITS==64"
#include <fts.h>
int main() {
}
----------------------->8-----------------------
Note, with older fakeroot, i.e. reverted [1] my simple build gets to the end
successfully.
[1]
https://git.buildroot.net/buildroot/commit/?h=f1350977634f96f0404b9801e6f79cb7200cf26d
[2]
https://salsa.debian.org/clint/fakeroot/-/commit/c465f716856cd561dba3522a4f5c714ea8bedfbd
[3]
https://sourceware.org/git/?p=glibc.git;a=commit;h=8b7b7f75d91f7bac323dd6a370aeb3e9c5c4a7d5
[4] https://github.com/mesonbuild/meson/issues/3519#issuecomment-386281558
--
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-08-11 22:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 22:11 bugzilla [this message]
2024-06-15 15:12 ` [Buildroot] [Bug 15721] fakeroot 1.32.1 fails to build on CentOS 7.x machines 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-15721-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