From: Rongqing Li <rongqing.li@windriver.com>
To: Phil Blundell <pb@pbcl.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] sstate.bbclass: fix parallel building issue
Date: Thu, 15 Aug 2013 18:08:35 +0800 [thread overview]
Message-ID: <520CA8A3.6050709@windriver.com> (raw)
In-Reply-To: <1376560519.17787.16.camel@phil-desktop.brightsign>
On 08/15/2013 05:55 PM, 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.
>
Good idea, use a symlink in autotools_copy_aclocal,
when tar makes a archive file, use -h parameter.
-h, --dereference
follow symlinks; archive and dump the files they point to
-Roy
> p.
>
>
>
>
--
Best Reagrds,
Roy | RongQing Li
next prev parent reply other threads:[~2013-08-15 10:08 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 [this message]
2013-08-15 16:23 ` Richard Purdie
2013-08-15 16:27 ` Mark Hatle
2013-08-15 23:04 ` Richard Purdie
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=520CA8A3.6050709@windriver.com \
--to=rongqing.li@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pb@pbcl.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