Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Sun, 28 Aug 2016 09:29:04 +0200	[thread overview]
Message-ID: <20160828092904.2a7d4e0e@free-electrons.com> (raw)
In-Reply-To: <20160827214849.GI5755@free.fr>

Hello,

On Sat, 27 Aug 2016 23:48:49 +0200, Yann E. MORIN wrote:

> >  * Introduce some glibc version dependency config knobs.  
> 
> That's unfortunately the only sane solution, I'm araid.
> 
> But that just for systemd is big a gun... :-/

Yes, it sucks :-/

> >  * Add a workaround in the systemd code to define O_TMPFILE to the
> >    proper value when not provided by the C library.  
> 
> At the same time, I'm not really happy with patching systemd...
> 
> O_TMPFILE is not the same value on all archs: generic, alpha, parisc and
> sparc.

I must say I still don't understand the overlap of the kernel headers
and glibc here. 

In the kernel, we have:

include/uapi/asm-generic/fcntl.h:#define __O_TMPFILE    020000000

In glibc, we have:

sysdeps/unix/sysv/linux/bits/fcntl-linux.h:# define __O_TMPFILE   (020000000 | __O_DIRECTORY)

Which is not even the same value.

Same for SPARC.

I'd still say that patching systemd is the easiest solution, and we
will be able to remove this patch once we get rid of those too old
toolchains (which we will have to do at some point, when they become
too annoying / irrelevant).

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-08-28  7:29 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
2016-08-27 21:48       ` Yann E. MORIN
2016-08-28  7:29         ` Thomas Petazzoni [this message]
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=20160828092904.2a7d4e0e@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