From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
peter.maydell@linaro.org
Subject: [Qemu-devel] [PATCH 0/3] build-sys: Exclude empty object files when linking libqemuutil.a
Date: Wed, 3 Sep 2014 11:44:53 +0800 [thread overview]
Message-ID: <1409715896-14322-1-git-send-email-famz@redhat.com> (raw)
On Mac OS X, ranlib complains on a few empty objects:
AR libqemuutil.a
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib:
file: libqemuutil.a(generated-tracers.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib:
file: libqemuutil.a(host-utils.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib:
file: libqemuutil.a(getauxval.o) has no symbols
This series fixes the warnings.
Fam
Fam Zheng (3):
trace: Only link generated-tracers.o with "simple" backend
util: Move general qemu_getauxval to util/getauxval.c
util: Don't link host-utils.o if it's empty
include/qemu/osdep.h | 4 ----
trace/Makefile.objs | 3 +--
util/Makefile.objs | 3 ++-
util/getauxval.c | 8 ++++++++
util/host-utils.c | 2 --
5 files changed, 11 insertions(+), 9 deletions(-)
--
2.1.0.27.g96db324
next reply other threads:[~2014-09-03 3:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 3:44 Fam Zheng [this message]
2014-09-03 3:44 ` [Qemu-devel] [PATCH 1/3] trace: Only link generated-tracers.o with "simple" backend Fam Zheng
2014-09-05 9:04 ` Stefan Hajnoczi
2014-09-03 3:44 ` [Qemu-devel] [PATCH 2/3] util: Move general qemu_getauxval to util/getauxval.c Fam Zheng
2014-09-03 3:44 ` [Qemu-devel] [PATCH 3/3] util: Don't link host-utils.o if it's empty Fam Zheng
2014-09-03 7:53 ` [Qemu-devel] [PATCH 0/3] build-sys: Exclude empty object files when linking libqemuutil.a Paolo Bonzini
2014-09-10 6:19 ` Fam Zheng
2014-09-10 8:23 ` Paolo Bonzini
2014-09-03 11:49 ` Peter Maydell
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=1409715896-14322-1-git-send-email-famz@redhat.com \
--to=famz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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.