From: Luiz Capitulino <lcapitulino@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>, aliguori@us.ibm.com
Subject: [Qemu-devel] Parallel build broken on master
Date: Fri, 30 Mar 2012 16:10:02 -0300 [thread overview]
Message-ID: <20120330161002.1cfc450d@doriath.home> (raw)
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.
next reply other threads:[~2012-03-30 19:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 19:10 Luiz Capitulino [this message]
2012-03-30 19:16 ` [Qemu-devel] Parallel build broken on master Paolo Bonzini
2012-03-30 19:21 ` Luiz Capitulino
2012-03-30 19:25 ` Anthony Liguori
2012-03-30 19:36 ` Paolo Bonzini
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=20120330161002.1cfc450d@doriath.home \
--to=lcapitulino@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=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 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.