From: Sasha Levin <levinsasha928@gmail.com>
To: Matt Evans <matt@ozlabs.org>
Cc: Asias He <asias.hejun@gmail.com>, KVM list <kvm@vger.kernel.org>,
Pekka Enberg <penberg@kernel.org>
Subject: Re: [PATCH V2] kvm tools: Add build target for statically-linked binary
Date: Sun, 29 Jan 2012 22:51:46 -0500 [thread overview]
Message-ID: <1327895506.6697.1.camel@lappy> (raw)
In-Reply-To: <4F260BEA.5030606@ozlabs.org>
On Mon, 2012-01-30 at 14:18 +1100, Matt Evans wrote:
> In lieu of any good lightweight solutions, can we include this patch as it is
> still useful for builds on systems without the offending optional libraries?
How about we do it as a 'make static' target which will generate a
static binary without optional libraries (or just libs that don't link
statically)?
--
Sasha.
next prev parent reply other threads:[~2012-01-30 3:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 5:10 [PATCH] kvm tools: Add build target for statically-linked binary Matt Evans
2012-01-09 6:45 ` [PATCH V2] " Matt Evans
2012-01-09 7:07 ` Pekka Enberg
2012-01-09 12:09 ` Sasha Levin
2012-01-09 7:51 ` Asias He
2012-01-30 3:18 ` Matt Evans
2012-01-30 3:51 ` Sasha Levin [this message]
2012-01-30 3:58 ` Matt Evans
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=1327895506.6697.1.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=asias.hejun@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=matt@ozlabs.org \
--cc=penberg@kernel.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