From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v3 00/15] preparation for autoconfy configure script
Date: Thu, 23 Dec 2010 11:43:47 +0100 [thread overview]
Message-ID: <1293101042-13121-1-git-send-email-pbonzini@redhat.com> (raw)
This is part two of the configure series. It does various miscellaneous
changes to the configure script that make it possible to later handle
an autoconfy command-line.
The rest is left for after 0.14, unless the release takes much more
than expected.
v1->v2
misc comments addressed
v2->v3
rebased, preserved Solaris compatibility for the three srcdir patches
(11 to 13).
Paolo Bonzini (15):
default compilation tools to environment variables
default make and install to environment variables
move feature variables to the top
fix sparse support (?)
test cc with the complete set of chosen flags
do not pass bogus $(SRC_PATH) include paths to cc during configure
provide portable HOST_LONG_BITS test
fix spelling of $pkg_config, move default together with other cross tools
do not default to non-prefixed pkg-config when cross compiling
reorganize sdl-config tests
move "ln -sf" emulation to a function
remove source_path_used
move --srcdir detection earlier
remove HOST_CC mention from roms/{sea,vga}bios/config.mak
make trace options use autoconfy names
configure | 438 +++++++++++++++++++++++++++-----------------------------
rules.mak | 6 +-
tests/Makefile | 3 +-
3 files changed, 216 insertions(+), 231 deletions(-)
--
1.7.3.2
next reply other threads:[~2010-12-23 10:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 10:43 Paolo Bonzini [this message]
2010-12-23 10:43 ` [Qemu-devel] [PATCH v3 01/15] default compilation tools to environment variables Paolo Bonzini
2010-12-23 10:43 ` [Qemu-devel] [PATCH v3 02/15] default make and install " Paolo Bonzini
2010-12-23 10:43 ` [Qemu-devel] [PATCH v3 03/15] move feature variables to the top Paolo Bonzini
2010-12-23 10:43 ` [Qemu-devel] [PATCH v3 04/15] fix sparse support (?) Paolo Bonzini
2010-12-23 10:43 ` [Qemu-devel] [PATCH v3 05/15] test cc with the complete set of chosen flags Paolo Bonzini
2010-12-23 10:43 ` [Qemu-devel] [PATCH v3 06/15] do not pass bogus $(SRC_PATH) include paths to cc during configure Paolo Bonzini
2010-12-23 10:43 ` [Qemu-devel] [PATCH v3 07/15] provide portable HOST_LONG_BITS test Paolo Bonzini
2010-12-23 10:43 ` [Qemu-devel] [PATCH v3 08/15] fix spelling of $pkg_config, move default together with other cross tools Paolo Bonzini
2010-12-23 10:43 ` [Qemu-devel] [PATCH v3 09/15] do not default to non-prefixed pkg-config when cross compiling Paolo Bonzini
2010-12-23 10:43 ` [Qemu-devel] [PATCH v3 10/15] reorganize sdl-config tests Paolo Bonzini
2010-12-23 10:43 ` [Qemu-devel] [PATCH v3 11/15] move "ln -sf" emulation to a function Paolo Bonzini
2010-12-23 10:43 ` [Qemu-devel] [PATCH v3 12/15] remove source_path_used Paolo Bonzini
2010-12-23 10:44 ` [Qemu-devel] [PATCH v3 13/15] move --srcdir detection earlier Paolo Bonzini
2010-12-23 10:44 ` [Qemu-devel] [PATCH v3 14/15] remove HOST_CC mention from roms/{sea, vga}bios/config.mak Paolo Bonzini
2010-12-23 10:44 ` [Qemu-devel] [PATCH v3 15/15] make trace options use autoconfy names Paolo Bonzini
2011-01-14 9:58 ` [Qemu-devel] Re: [PATCH v3 00/15] preparation for autoconfy configure script Paolo Bonzini
2011-01-14 17:57 ` Blue Swirl
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=1293101042-13121-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@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).