From: "Daniel P. Berrange" <berrange@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] buildsys: Move -lnettle and -lgnutls to per object variables
Date: Tue, 5 Sep 2017 16:25:24 +0100 [thread overview]
Message-ID: <20170905152524.GF311@redhat.com> (raw)
In-Reply-To: <20170905151319.10756-1-famz@redhat.com>
On Tue, Sep 05, 2017 at 11:13:17PM +0800, Fam Zheng wrote:
> Not all targets need the flags and libs of nettle/gnutls, so move
> them out from global variables, as done with other libraries.
>
> Fam Zheng (2):
> buildsys: Move nettle cflags/libs to per object
> buildsys: Move gnutls cflags/libs to per object
The same change for 'gcrypt' is needed
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2017-09-05 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 15:13 [Qemu-devel] [PATCH 0/2] buildsys: Move -lnettle and -lgnutls to per object variables Fam Zheng
2017-09-05 15:13 ` [Qemu-devel] [PATCH 1/2] buildsys: Move nettle cflags/libs to per object Fam Zheng
2017-09-05 15:13 ` [Qemu-devel] [PATCH 2/2] buildsys: Move gnutls " Fam Zheng
2017-09-05 15:25 ` Daniel P. Berrange [this message]
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=20170905152524.GF311@redhat.com \
--to=berrange@redhat.com \
--cc=famz@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).