From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [4931] Enable VDE by default if library is present.
Date: Wed, 23 Jul 2008 18:14:34 +0000 [thread overview]
Message-ID: <E1KLirC-00019V-9y@cvs.savannah.gnu.org> (raw)
Revision: 4931
http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=4931
Author: aliguori
Date: 2008-07-23 18:14:33 +0000 (Wed, 23 Jul 2008)
Log Message:
-----------
Enable VDE by default if library is present.
VDE isn't used unless the user explicitly asks for it so if the library is
present on the system, we should include support for it.
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Modified Paths:
--------------
trunk/configure
Modified: trunk/configure
===================================================================
--- trunk/configure 2008-07-23 16:35:45 UTC (rev 4930)
+++ trunk/configure 2008-07-23 18:14:33 UTC (rev 4931)
@@ -89,7 +89,7 @@
EXESUF=""
gdbstub="yes"
slirp="yes"
-vde="no"
+vde="yes"
fmod_lib=""
fmod_inc=""
vnc_tls="yes"
@@ -281,7 +281,7 @@
;;
--disable-slirp) slirp="no"
;;
- --enable-vde) vde="yes"
+ --disable-vde) vde="no"
;;
--disable-kqemu) kqemu="no"
;;
@@ -435,7 +435,7 @@
echo " --fmod-inc path to FMOD includes"
echo " --enable-uname-release=R Return R for uname -r in usermode emulation"
echo " --sparc_cpu=V Build qemu for Sparc architecture v7, v8, v8plus, v8plusa, v9"
-echo " --enable-vde enable support for vde network [$vde]"
+echo " --disable-vde disable support for vde network"
echo ""
echo "NOTE: The object files are built at the place where configure is launched"
exit 1
@@ -735,11 +735,7 @@
if $cc $ARCH_CFLAGS -o $TMPE $TMPC 2> /dev/null ; then
:
else
- echo
- echo "Error: VDE check failed"
- echo "Make sure to have the VDE libs and headers installed."
- echo
- exit 1
+ vde="no"
fi
fi
reply other threads:[~2008-07-23 18:14 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=E1KLirC-00019V-9y@cvs.savannah.gnu.org \
--to=anthony@codemonkey.ws \
--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).