Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] package/systemd: fix build with old toolchains
Date: Tue, 30 Aug 2016 11:48:10 +0200	[thread overview]
Message-ID: <20160830094810.GC5815@free.fr> (raw)
In-Reply-To: <20160830093511.ykvjhugty2xhg4rf@tarshish>

Baruch, All,

On 2016-08-30 12:35 +0300, Baruch Siach spake thusly:
> Hi Yann,
> 
> On Tue, Aug 30, 2016 at 11:29:37AM +0200, Yann E. MORIN wrote:
> > Toolchains using glibc-2.18 or older do not define O_TMPFILE, which
> > causes build failures on some archs.
> > 
> > systemd has a definition for O_TMPFILE if it is missing, but only
> > defines it for i386 or x86_64. Furthermore, the header defining it is
> > not included everywhere O_TMPFILE is used.
> > 
> > Fix that with three patches backported from upstream:
> >   - include the needed header where it is needed (he!),
> >   - define O_TMPFILE for all archs, according to linux-4.8rc3,
> >   - no longer guard against undefined O_TMPFILE in fileio.
> 
> This last patch is not a pure build fix, but more of a feature enhancement. 
> Don't know if it fits in master.

Well, it's indeed not a _pure_ bug fix, but given that O_TMPFILE is now
always defined, the guards are no longer needed at all: they will never
be guarding anything now.

Besides, using O_TMPFILE is way better than not using it; it makes the
thing a little bit more secure.

> Also, your patches are missing sign-off.

Damn. Upstream is not using SoB lines (Lennart asked me to remove them
[0] and I fiorgot to re-add them when adding them in Buildroot; the
previosu iteration did have my SoB lines).

> An autobuild reference in the commit log would also be nice.

Damn, I also forgot that... :-/

Thanks!

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2016-08-30  9:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-30  9:29 [Buildroot] [PATCHv2] package/systemd: fix build with old toolchains Yann E. MORIN
2016-08-30  9:35 ` Baruch Siach
2016-08-30  9:48   ` Yann E. MORIN [this message]
2016-09-18 14:05 ` 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=20160830094810.GC5815@free.fr \
    --to=yann.morin.1998@free.fr \
    --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