qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Parallel build broken on master
Date: Fri, 30 Mar 2012 21:36:58 +0200	[thread overview]
Message-ID: <jl520s$vge$1@dough.gmane.org> (raw)
In-Reply-To: <4F7608AE.302@codemonkey.ws>

Il 30/03/2012 21:25, Anthony Liguori ha scritto:
> On 03/30/2012 02:21 PM, Luiz Capitulino wrote:
>> On Fri, 30 Mar 2012 21:16:03 +0200
>> Paolo Bonzini<pbonzini@redhat.com>  wrote:
>>
>>> Il 30/03/2012 21:10, Luiz Capitulino ha scritto:
>>>> Hi,
>>>>
>>>> The HEAD is 6b7cff76. Will paste the configure I use because they
>>>> seem to make
>>>> the bug more likely:
>>>>
>>>> $ ../configure --target-list=x86_64-softmmu --disable-strip
>>>> --enable-debug \
>>>>    --disable-xen --disable-brlapi --disable-curses --disable-curl \
>>>>    --disable-bluez --disable-system --disable-debug-tcg
>>>> --audio-card-list=
>>>> $ make -j2
>>>> [...]
>>>>    LINK  qemu-nbd
>>>> gcc: error: aes.o: No such file or directory
>>>> gcc: error: aio.o: No such file or directory
>>>> gcc: error: async.o: No such file or directory
>>>> gcc: error: block.o: No such file or directory
>>>> gcc: error: block/blkdebug.o: No such file or directory
>>>> gcc: error: block/blkverify.o: No such file or directory
>>>> gcc: error: block/bochs.o: No such file or directory
>>>> gcc: error: block/cloop.o: No such file or directory
>>>> gcc: error: block/cow.o: No such file or directory
>>>> gcc: error: block/dmg.o: No such file or directory
>>>> gcc: error: block/nbd.o: No such file or directory
>>>> gcc: error: block/parallels.o: No such file or directory
>>>> gcc: error: block/qcow.o: No such file or directory
>>>> gcc: error: block/qcow2-cache.o: No such file or directory
>>>> gcc: error: block/qcow2-cluster.o: No such file or directory
>>>> [...]
>>>>
>>>> Doesn't happen with -j1 and doesn't happen if I test with commit
>>>> 040b66f3f9
>>>> (ie. before the qtest series).
>>>>
>>>> I build from a separate dir, btw.
>>>
>>> Can you bisect?  Likely it's 1/7 though.
>>
>> Indeed, bisect says it's b93b63f574.
> 
> Can you provide the output of V=1 and config.log?
> 
> make -j9 works for me just fine.

-j4 works, -j2 fails (from a clean directory).  /me wonders if it is a
make bug.  I remember GCC hitting one.

Paolo

  reply	other threads:[~2012-03-30 19:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-30 19:10 [Qemu-devel] Parallel build broken on master Luiz Capitulino
2012-03-30 19:16 ` Paolo Bonzini
2012-03-30 19:21   ` Luiz Capitulino
2012-03-30 19:25     ` Anthony Liguori
2012-03-30 19:36       ` Paolo Bonzini [this message]
2012-03-30 19:52       ` Luiz Capitulino

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='jl520s$vge$1@dough.gmane.org' \
    --to=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).