From: malc <av1474@comtv.ru>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [4826] Fix test arguments (Jeremy C.
Date: Wed, 02 Jul 2008 18:13:46 +0000 [thread overview]
Message-ID: <E1KE6pu-00086E-FB@cvs.savannah.gnu.org> (raw)
Revision: 4826
http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=4826
Author: malc
Date: 2008-07-02 18:13:46 +0000 (Wed, 02 Jul 2008)
Log Message:
-----------
Fix test arguments (Jeremy C. Reed)
Modified Paths:
--------------
trunk/configure
Modified: trunk/configure
===================================================================
--- trunk/configure 2008-07-02 18:03:12 UTC (rev 4825)
+++ trunk/configure 2008-07-02 18:13:46 UTC (rev 4826)
@@ -1042,7 +1042,7 @@
echo " &${drv}_audio_driver, \\" >>$config_h
def=CONFIG_`echo $drv | tr '[:lower:]' '[:upper:]'`
echo "$def=yes" >> $config_mak
- if test "$drv" == "fmod"; then
+ if test "$drv" = "fmod"; then
echo "CONFIG_FMOD_LIB=$fmod_lib" >> $config_mak
echo "CONFIG_FMOD_INC=$fmod_inc" >> $config_mak
fi
reply other threads:[~2008-07-02 18:13 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=E1KE6pu-00086E-FB@cvs.savannah.gnu.org \
--to=av1474@comtv.ru \
--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).