From: Hollis Blanchard <hollis@penguinppc.org>
To: qemu-devel@nongnu.org
Cc: blauwirbel@gmail.com, kvm-ppc@vger.kernel.org
Subject: [PATCH 1/4] Fix "make install" with a cross toolchain
Date: Thu, 05 Aug 2010 00:21:34 +0000 [thread overview]
Message-ID: <1280967697-1875-2-git-send-email-hollis@penguinppc.org> (raw)
In-Reply-To: <1280967697-1875-1-git-send-email-hollis@penguinppc.org>
We must be able to use a non-native strip executable, but not all
versions of 'install' support the --strip-program option (e.g.
OpenBSD). Accordingly, we can't use 'install -s', and we must run strip
separately.
Signed-off-by: Hollis Blanchard <hollis@penguinppc.org>
Cc: blauwirbel@gmail.com
---
Makefile.target | 5 ++++-
configure | 4 +++-
2 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/Makefile.target b/Makefile.target
index 8a9c427..00bf6f9 100644
--- a/Makefile.target
+++ b/Makefile.target
@@ -326,7 +326,10 @@ clean:
install: all
ifneq ($(PROGS),)
- $(INSTALL) -m 755 $(STRIP_OPT) $(PROGS) "$(DESTDIR)$(bindir)"
+ $(INSTALL) -m 755 $(PROGS) "$(DESTDIR)$(bindir)"
+ifneq ($(STRIP),)
+ $(STRIP) $(patsubst %,"$(DESTDIR)$(bindir)/%",$(PROGS))
+endif
endif
# Include automatically generated dependency files
diff --git a/configure b/configure
index a20371c..146dac0 100755
--- a/configure
+++ b/configure
@@ -80,6 +80,7 @@ make="make"
install="install"
objcopy="objcopy"
ld="ld"
+strip="strip"
helper_cflags=""
libs_softmmu=""
libs_tools=""
@@ -125,6 +126,7 @@ cc="${cross_prefix}${cc}"
ar="${cross_prefix}${ar}"
objcopy="${cross_prefix}${objcopy}"
ld="${cross_prefix}${ld}"
+strip="${cross_prefix}${strip}"
# default flags for all hosts
QEMU_CFLAGS="-fno-strict-aliasing $QEMU_CFLAGS"
@@ -2227,7 +2229,7 @@ if test "$debug" = "yes" ; then
echo "CONFIG_DEBUG_EXEC=y" >> $config_host_mak
fi
if test "$strip_opt" = "yes" ; then
- echo "STRIP_OPT=-s" >> $config_host_mak
+ echo "STRIP=${strip}" >> $config_host_mak
fi
if test "$bigendian" = "yes" ; then
echo "HOST_WORDS_BIGENDIAN=y" >> $config_host_mak
--
1.7.2
next prev parent reply other threads:[~2010-08-05 0:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 0:21 [PATCH 0/4] fix PowerPC 440 Bamboo platform emulation Hollis Blanchard
2010-08-05 0:21 ` Hollis Blanchard [this message]
2010-08-05 0:21 ` [PATCH 2/4] ppc4xx: correct SDRAM controller warning message condition Hollis Blanchard
2010-08-05 0:21 ` [PATCH 3/4] ppc4xx: don't unregister RAM at reset Hollis Blanchard
2010-08-05 0:21 ` [PATCH 4/4] ppc4xx: load Bamboo kernel, initrd, and fdt at fixed addresses Hollis Blanchard
2010-08-05 4:57 ` [Qemu-devel] [PATCH 4/4] ppc4xx: load Bamboo kernel, initrd, Edgar E. Iglesias
2010-08-06 2:39 ` [PATCH 4/4] ppc4xx: load Bamboo kernel, initrd, and fdt at fixed addresses Liu Yu-B13201
2010-08-06 17:55 ` [PATCH 4/4] ppc4xx: load Bamboo kernel, initrd, and fdt at fixed Hollis Blanchard
2010-08-06 18:12 ` [Qemu-devel] Re: [PATCH 4/4] ppc4xx: load Bamboo kernel, Edgar E. Iglesias
2010-08-05 5:01 ` [Qemu-devel] [PATCH 0/4] fix PowerPC 440 Bamboo platform Edgar E. Iglesias
2010-08-19 17:24 ` [PATCH 0/4] fix PowerPC 440 Bamboo platform emulation Hollis Blanchard
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=1280967697-1875-2-git-send-email-hollis@penguinppc.org \
--to=hollis@penguinppc.org \
--cc=blauwirbel@gmail.com \
--cc=kvm-ppc@vger.kernel.org \
--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