From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/systemd: importd broken on Sourcery CodeBench ARM 2014.05
Date: Mon, 11 Jul 2016 11:02:25 +0200 [thread overview]
Message-ID: <20160711110225.19dfaa5f@free-electrons.com> (raw)
In-Reply-To: <1468187781-7497-1-git-send-email-yann.morin.1998@free.fr>
Hello,
On Sun, 10 Jul 2016 23:56:21 +0200, Yann E. MORIN wrote:
> This toolchain uses glibc-2.18, which is tool old to provide O_TMPFILE,
> which was added only in glibc-2.19.
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> ---
> package/systemd/Config.in | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/package/systemd/Config.in b/package/systemd/Config.in
> index 4a2aa33..48e6c45 100644
> --- a/package/systemd/Config.in
> +++ b/package/systemd/Config.in
> @@ -145,6 +145,8 @@ config BR2_PACKAGE_SYSTEMD_IMPORTD
> bool "enable import daemon"
> depends on BR2_PACKAGE_LIBGPG_ERROR_ARCH_SUPPORTS # libgcrypt
> depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_11 # O_TMPFILE
> + # This toolchain has glibc-2.18, too old to provide O_TMPFILE
> + depends on !BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM
So is the problem a kernel headers problem, or a glibc version problem ?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-07-11 9:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-10 21:56 [Buildroot] [PATCH] package/systemd: importd broken on Sourcery CodeBench ARM 2014.05 Yann E. MORIN
2016-07-11 9:02 ` Thomas Petazzoni [this message]
2016-07-11 17:16 ` Yann E. MORIN
2016-08-27 21:32 ` Thomas Petazzoni
2016-08-27 21:48 ` Yann E. MORIN
2016-08-28 7:29 ` Thomas Petazzoni
2016-08-28 14:36 ` Yann E. MORIN
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=20160711110225.19dfaa5f@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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