From: Paolo Bonzini <pbonzini@redhat.com>
To: Bug 1324112 <1324112@bugs.launchpad.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1324112] [NEW] qemu parallel building error on libcacard.la
Date: Thu, 10 Jul 2014 09:43:16 +0200 [thread overview]
Message-ID: <53BE4414.7020006@redhat.com> (raw)
In-Reply-To: <6D74E24018EBA548A6FC5B2CE98D10AB17639F@ezex10.ezchip.com>
Il 10/06/2014 17:08, tal zilcer ha scritto:
> Trace/generated*.o files depends on trace/generated*.la files($(libcacard-obj-y): | $(libcacard-lobj-y))
> Also util depends on generated-*.o files (util-obj-y += generated-events.o)
> This means when libcacard.la is being build generated-*.o files can be build by the util target.
> I think you should change libcacard.la dependencies to include the o files and not only the la files.
This should now be fixed because libcacard doesn't use trace/* anymore.
In any case, this was the logic:
- trace/generated-events.o should not be started until after
trace/generated-events.lo has been built.
- trace/generated-events.lo will also build trace/generated-events.o, so
the trace/generated-events.o rule will never be invoked.
Paolo
next prev parent reply other threads:[~2014-07-10 7:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140528125211.29732.51513.malonedeb@wampee.canonical.com>
2014-06-04 8:19 ` [Qemu-devel] [Bug 1324112] [NEW] qemu parallel building error on libcacard.la Stefan Hajnoczi
2014-06-04 3:33 ` tal zilcer
2014-06-09 13:38 ` Stefan Hajnoczi
2014-06-10 9:41 ` tal zilcer
2014-06-10 12:45 ` tal zilcer
2014-06-10 15:08 ` tal zilcer
2014-07-10 7:43 ` Paolo Bonzini [this message]
2014-06-10 16:35 ` tal zilcer
2014-07-09 7:49 ` Stefan Hajnoczi
2014-07-09 10:06 ` Peter Maydell
2014-07-10 5:28 ` [Qemu-devel] [Bug 1324112] " Fam Zheng
2014-07-10 7:32 ` Stefan Hajnoczi
2014-07-10 7:42 ` Stefan Hajnoczi
2014-07-10 7:49 ` Stefan Hajnoczi
2016-06-15 12:42 ` T. Huth
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=53BE4414.7020006@redhat.com \
--to=pbonzini@redhat.com \
--cc=1324112@bugs.launchpad.net \
--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.