linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rongqing Li <rongqing.li@windriver.com>
To: <dsterba@suse.cz>, <linux-btrfs@vger.kernel.org>, <sandeen@redhat.com>
Subject: Re: [PATCH] btrfs-progs: Add dependencies explicitly to fix a parallel build issue
Date: Sun, 22 Sep 2013 09:06:39 +0800	[thread overview]
Message-ID: <523E429F.8010606@windriver.com> (raw)
In-Reply-To: <20130918145117.GC6810@twin.jikos.cz>



On 09/18/2013 10:51 PM, David Sterba wrote:
> On Wed, Sep 18, 2013 at 09:11:01AM +0800, rongqing.li@windriver.com wrote:
>> From: Roy Li <rongqing.li@windriver.com>
>>
>> The dependencies of "all: version.h" or other similar ones can not
>> fix the parallel build failure, only reduce the times; In fact,
>> many *.o files require version.h file.
>>
>> 	#grep '#include "version.h"' ./ -r
>> 	./btrfs-corrupt-block.c:#include "version.h"
>> 	./btrfs.c:#include "version.h"
>> 	./btrfs-image.c:#include "version.h"
>> 	./cmds-filesystem.c:#include "version.h"
>> 	./btrfs-show-super.c:#include "version.h"
>> 	./btrfs-select-super.c:#include "version.h"
>> 	./cmds-restore.c:#include "version.h"
>> 	./btrfs-find-root.c:#include "version.h"
>> 	./mkfs.c:#include "version.h"
>> 	./btrfs-zero-log.c:#include "version.h"
>> 	./btrfs-defrag.c:#include "version.h"
>> 	./cmds-chunk.c:#include "version.h"
>> 	./btrfstune.c:#include "version.h"
>> 	./btrfs-calc-size.c:#include "version.h"
>> 	./btrfs-map-logical.c:#include "version.h"
>> 	./cmds-check.c:#include "version.h"
>> 	./btrfs-debug-tree.c:#include "version.h"
>>
>> Signed-off-by: Roy Li <rongqing.li@windriver.com>
>> ---
>>   Sorry, The patch [btrfs-progs: fix parallel build] sent by me on Sep 3
>> can not fix the build failure, when build enough times on a 16 core cpu,
>> the build failure happens again, so I refix it again.
>
> I'm running make -j all the time but haven't seen the build fail due to
> missing version.h for a long time. With this patch or the previous one
> or with Eric's, all fine. The generated dependency files contain
> version.h so make has complete information how to order the rules.
>

I want to know how many cores your cpu has? I can not reproduce it on
my 2 cores cpu, but it always happens when run on a server which is
a 16 cores cpu and "make -j20"


> The dependency files are generated by an implicit rule .c -> .o.d, so
> there should be no problem for any of the files listed above.
>

Do you means the below:

.c.o:
         $(Q)$(check) $<
         @echo "    [CC]     $@"
         $(Q)$(CC) $(DEPFLAGS) $(AM_CFLAGS) $(CFLAGS) -c $<


-Roy



> If you think the patch "btrfs-progs: fix parallel build" does not help
> much I'll drop it.
>
>
> david
>
>

-- 
Best Reagrds,
Roy | RongQing Li

  reply	other threads:[~2013-09-22  1:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-18  1:11 [PATCH] btrfs-progs: Add dependencies explicitly to fix a parallel build issue rongqing.li
2013-09-18  1:51 ` Eric Sandeen
2013-09-18  1:55   ` Rongqing Li
2013-09-23  7:17   ` Rongqing Li
2013-09-18  1:56 ` [PATCH] btrfs-progs: Add version.h dependency to fix parallel builds Eric Sandeen
2013-09-18  2:26   ` Eric Sandeen
2013-09-18  6:39     ` Rongqing Li
2013-09-18 14:51 ` [PATCH] btrfs-progs: Add dependencies explicitly to fix a parallel build issue David Sterba
2013-09-22  1:06   ` Rongqing Li [this message]
2013-09-23 12:26     ` David Sterba

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=523E429F.8010606@windriver.com \
    --to=rongqing.li@windriver.com \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sandeen@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).