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: Sat, 27 Aug 2016 23:32:27 +0200 [thread overview]
Message-ID: <20160827233227.27f54621@free-electrons.com> (raw)
In-Reply-To: <20160711171630.GD3734@free.fr>
Hello,
On Mon, 11 Jul 2016 19:16:30 +0200, Yann E. MORIN wrote:
> > So is the problem a kernel headers problem, or a glibc version problem ?
>
> Both. O_TMPFILE was introduced in Linux 3.11, so we need at least those
> headers. Also, glibc-2.18 did not provide it in fcntl.h; it only
> appeared in glibc-2.19.
I'm still not sure to understand why both are needed.
In any case, this fix is not correct, since the issue appears with
other toolchains as well:
http://autobuild.buildroot.net/results/e6f/e6f8189029487155a784b4e664178adfd92f8884/build-end.log
This one is an ARM toolchain, that uses 3.12 kernel headers, so most
likely it's a glibc version issue.
http://autobuild.buildroot.net/results/339/33912eebb5f4ee3f73be078ba2035f48d76a6a46/build-end.log
This one is a PowerPC toolchain.
I see two possibilities only:
* Introduce some glibc version dependency config knobs.
* Add a workaround in the systemd code to define O_TMPFILE to the
proper value when not provided by the C library.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-27 21:32 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
2016-07-11 17:16 ` Yann E. MORIN
2016-08-27 21:32 ` Thomas Petazzoni [this message]
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=20160827233227.27f54621@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