From: Thiemo Seufer <ths@networkno.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] Fix some configure/Makefile weirdness
Date: Thu, 21 Dec 2006 19:00:27 +0000 [thread overview]
Message-ID: <20061221190027.GA7239@networkno.de> (raw)
Hello All,
the appended patch allows for propagating CFLAGS and LDFLAGS to the host
Makefile. This reactivates the (undocumented) --extra-cflags= and
--extra-ldflags= options of configure which are currently NOPs.
It also removes the CFLAGS=-O2 default from configure since it is
already hardcoded in Makefile and Makefile.target.
Comments?
Thiemo
Index: Makefile
===================================================================
RCS file: /sources/qemu/qemu/Makefile,v
retrieving revision 1.106
diff -u -p -r1.106 Makefile
--- Makefile 5 Aug 2006 21:29:27 -0000 1.106
+++ Makefile 21 Dec 2006 18:48:34 -0000
@@ -5,14 +5,14 @@ include config-host.mak
.PHONY: all clean distclean dvi info install install-doc tar tarbin \
speed test test2 html dvi info
-CFLAGS=-Wall -O2 -g -fno-strict-aliasing -I.
+CFLAGS+=-Wall -O2 -g -fno-strict-aliasing -I.
ifdef CONFIG_DARWIN
CFLAGS+= -mdynamic-no-pic
endif
ifeq ($(ARCH),sparc)
CFLAGS+=-mcpu=ultrasparc
endif
-LDFLAGS=-g
+LDFLAGS+=-g
LIBS=
DEFINES+=-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
TOOLS=qemu-img$(EXESUF)
Index: configure
===================================================================
RCS file: /sources/qemu/qemu/configure,v
retrieving revision 1.113
diff -u -p -r1.113 configure
--- configure 19 Dec 2006 03:31:34 -0000 1.113
+++ configure 21 Dec 2006 18:48:34 -0000
@@ -243,11 +243,6 @@ for opt do
esac
done
-# Checking for CFLAGS
-if test -z "$CFLAGS"; then
- CFLAGS="-O2"
-fi
-
if test x"$show_help" = x"yes" ; then
cat << EOF
reply other threads:[~2006-12-21 19:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20061221190027.GA7239@networkno.de \
--to=ths@networkno.de \
--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 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.