From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] mtree: new package
Date: Wed, 27 Mar 2019 20:18:03 +0100 [thread overview]
Message-ID: <20190327201803.6b1a832d@windsurf> (raw)
In-Reply-To: <20190326142411.6943-1-esben.haabendal@gmail.com>
Hello Esben,
On Tue, 26 Mar 2019 15:24:11 +0100
Esben Haabendal <esben.haabendal@gmail.com> wrote:
> diff --git a/package/mtree/Config.in b/package/mtree/Config.in
> new file mode 100644
> index 000000000000..175d05d3bb0d
> --- /dev/null
> +++ b/package/mtree/Config.in
> @@ -0,0 +1,15 @@
> +config BR2_PACKAGE_MTREE
> + bool "mtree"
> + # mtree uses <fts.h> which is not included by default in uClibc
> + depends on BR2_TOOLCHAIN_USES_GLIBC
> + # fts.h does not support LFS (_FILE_OFFSET_BITS==64) in glibc versions
> + # older than 2.23, and codesourcery-arm is currently using glibc 2.18
> + depends on !BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM
My memory is a bit fuzzy on this, but we have some workarounds for this
issue in other packages:
# Undefining _FILE_OFFSET_BITS here because of a "bug" with glibc fts.h
# large file support. See https://bugzilla.redhat.com/show_bug.cgi?id=574992
# for more information.
LIBCGROUP_CONF_ENV = \
CXXFLAGS="$(TARGET_CXXFLAGS) -U_FILE_OFFSET_BITS" \
CFLAGS="$(TARGET_CFLAGS) -U_FILE_OFFSET_BITS"
# Undefining _FILE_OFFSET_BITS here because of a "bug" with glibc fts.h
# large file support.
# See https://bugzilla.redhat.com/show_bug.cgi?id=574992 for more information
RESTORECOND_MAKE_OPTS += \
$(TARGET_CONFIGURE_OPTS) \
CFLAGS="$(TARGET_CFLAGS) -U_FILE_OFFSET_BITS" \
CPPFLAGS="$(TARGET_CPPFLAGS) -U_FILE_OFFSET_BITS" \
ARCH="$(BR2_ARCH)"
and in a few other places.
Is it the same problem ? If it has been resolved in glibc 2.23, should
we remove those work-arounds ?
I just would like to make sure we don't work around this problem in
different ways in different packages.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-03-27 19:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 14:24 [Buildroot] [PATCH v4] mtree: new package Esben Haabendal
2019-03-27 19:18 ` Thomas Petazzoni [this message]
2019-03-27 22:28 ` Esben Haabendal
2019-03-28 11:14 ` Thomas Petazzoni
2019-03-28 15:14 ` Esben Haabendal
2019-03-28 18:13 ` Arnout Vandecappelle
2019-03-28 20:00 ` Thomas Petazzoni
2019-03-28 20:59 ` Peter Korsgaard
2019-03-28 21:53 ` Thomas Petazzoni
2019-03-29 9:31 ` Arnout Vandecappelle
2019-03-29 9:35 ` Thomas Petazzoni
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=20190327201803.6b1a832d@windsurf \
--to=thomas.petazzoni@bootlin.com \
--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