Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] sstate.bbclass: fix parallel building issue
Date: Fri, 16 Aug 2013 00:04:01 +0100	[thread overview]
Message-ID: <1376607841.22952.103.camel@ted> (raw)
In-Reply-To: <520D0174.7030901@windriver.com>

On Thu, 2013-08-15 at 11:27 -0500, Mark Hatle wrote:
> On 8/15/13 11:23 AM, Richard Purdie wrote:
> > On Thu, 2013-08-15 at 10:55 +0100, Phil Blundell wrote:
> >> On Thu, 2013-08-15 at 17:51 +0800, Rongqing Li wrote:
> >>> OK, But your issue is not related to me.
> >>>
> >>> I can reproduce my issue by two simple script.
> >>
> >> If tar is deciding that the file has "changed" just because the link
> >> count on the dentry has increased, that sounds like it is probably a bug
> >> in tar and ought to be fixed there.
> >>
> >> That said, I can't immediately think why autotools_copy_aclocal couldn't
> >> use a symlink rather than a hard link which would avoid this whole
> >> problem.  If the file is in the sysroot then there should be no risk of
> >> it going away underneath its user.
> >
> > Sadly this doesn't work. We block copy a set of .m4 files from the
> > sysroot. We can be running do_configure of package A whilst package B is
> > de-installed from the sysroot and this leads to files disappearing
> > whilst they're being accessed. Its turned out to be a really awkward
> > problem to fix.
> 
> Do we need some kind of a read/write lock on accessing those files.  (Is this 
> even something that we can do easily though the existing mechanisms?)

It would kill performance for no good reason, been there, looked at
it...

Cheers,

Richard



  reply	other threads:[~2013-08-15 23:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-13  8:20 [PATCH 0/1] sstate.bbclass: fix parallel building issue rongqing.li
2013-08-13  8:20 ` [PATCH 1/1] " rongqing.li
2013-08-13 19:02   ` Saul Wold
2013-08-14  5:28     ` Rongqing Li
2013-08-14  6:56       ` Martin Jansa
2013-08-14  9:27         ` Rongqing Li
2013-08-14 10:46         ` Richard Purdie
2013-08-14 10:59           ` Martin Jansa
2013-08-15  9:51             ` Rongqing Li
2013-08-15  9:55               ` Phil Blundell
2013-08-15 10:08                 ` Rongqing Li
2013-08-15 16:23                 ` Richard Purdie
2013-08-15 16:27                   ` Mark Hatle
2013-08-15 23:04                     ` Richard Purdie [this message]
2013-08-16  8:25                       ` Rongqing Li
2013-08-16  9:05                         ` Rongqing Li
2013-08-16  9:27                           ` Richard Purdie
2013-08-15 16:38                   ` Phil Blundell
2013-09-12 15:39   ` Richard Purdie

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=1376607841.22952.103.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox