All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: "Pádraig Brady" <P@draigBrady.com>, util-linux@vger.kernel.org
Subject: Re: [PATCH] build-sys: fix parallel builds w/setarch links
Date: Sun, 10 May 2015 12:20:43 -0500	[thread overview]
Message-ID: <554F936B.3010305@gmail.com> (raw)
In-Reply-To: <20150510152844.GJ30924@vapier>

Mike Frysinger wrote:
> On 05 May 2015 11:37, Pádraig Brady wrote:
>> On 04/05/15 04:51, Mike Frysinger wrote:
>>> From: Mike Frysinger <vapier@chromium.org>
>>>
>>> The symlink generation tries to write to the sys-utils/ subdir but does
>>> not make sure that dir exists.  This can sometimes lead to parallel build
>>> failures when building out-of-tree
>>
>>>   $(SETARCH_MAN_LINKS):
>>> +	$(AM_V_at) test -d $(dir $@) || mkdir -p $(dir $@)
>>>   	$(AM_V_GEN)echo ".so man8/setarch.8" > $@
>>>
>>>   install-exec-hook-setarch:
>>
>> The `test -d ... ||` bit is racy and redundant I think
>
> i noticed that, but i didn't bother fixing it -- i just copied & pasted from an
> earlier fix in this project which used the same exact line
>
> note: it's really only racy if mkdir itself fails internally, and i'm kind of
> the opinion that mkdir itself should be handling this
> -mike

Why do the test at all?  Why not just a simple `mkdir -p $(dir $@)` ?

   -- Bruce


  reply	other threads:[~2015-05-10 17:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-04  3:51 [PATCH] build-sys: fix parallel builds w/setarch links Mike Frysinger
2015-05-05 10:37 ` Pádraig Brady
2015-05-10 15:28   ` Mike Frysinger
2015-05-10 17:20     ` Bruce Dubbs [this message]
2015-05-10 20:38   ` Isaac Dunham
2015-05-11  8:05     ` Karel Zak
2015-05-16 17:50       ` Peter Cordes
2015-05-17  5:53         ` Mike Frysinger
2015-05-05 10:47 ` Karel Zak

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=554F936B.3010305@gmail.com \
    --to=bruce.dubbs@gmail.com \
    --cc=P@draigBrady.com \
    --cc=util-linux@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.