qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Bug 1324112 <1324112@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1324112] [NEW] qemu parallel building error	on libcacard.la
Date: Mon, 9 Jun 2014 15:38:01 +0200	[thread overview]
Message-ID: <20140609133801.GH19546@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <6D74E24018EBA548A6FC5B2CE98D10AB16DC2F@ezex10.ezchip.com>

[-- Attachment #1: Type: text/plain, Size: 438 bytes --]

On Wed, Jun 04, 2014 at 03:33:34AM -0000, tal zilcer wrote:
> Version 2.0.0
> 
> Isn’t the libcacard Makefile run as a recursive make?
> how do you keep the dependencies between two different makes(libcacard and trace)?

In qemu.git/master:Makefile I see:
ifeq ($(CONFIG_SMARTCARD_NSS),y)
include $(SRC_PATH)/libcacard/Makefile
endif

That doesn't look like recursive make to me, but maybe I'm missing
something.

Stefan

[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2014-06-09 13:38 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 [this message]
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
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=20140609133801.GH19546@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.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 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).