[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[or-cvs] r18239: {tor} Do not use == in our shell code; = is standard. (tor/trunk)
Author: nickm
Date: 2009-01-22 14:06:28 -0500 (Thu, 22 Jan 2009)
New Revision: 18239
Modified:
tor/trunk/ChangeLog
tor/trunk/configure.in
Log:
Do not use == in our shell code; = is standard.
Modified: tor/trunk/ChangeLog
===================================================================
--- tor/trunk/ChangeLog 2009-01-22 17:38:57 UTC (rev 18238)
+++ tor/trunk/ChangeLog 2009-01-22 19:06:28 UTC (rev 18239)
@@ -9,6 +9,8 @@
- Solve a bug that kept hardware crypto acceleration from getting
enabled when accounting was turned on. Fixes bug 907. Bugfix on
0.0.9pre6.
+ - Remove a bash-ism from configure.in to build properly on non-Linux
+ platforms. Bugfix on 0.2.1.1-alpha.
o Minor features:
- Support platforms where time_t is 64 bits long. (Congratulations,
Modified: tor/trunk/configure.in
===================================================================
--- tor/trunk/configure.in 2009-01-22 17:38:57 UTC (rev 18238)
+++ tor/trunk/configure.in 2009-01-22 19:06:28 UTC (rev 18239)
@@ -48,7 +48,7 @@
[Defined if we try to use freelists for buffer RAM chunks])
fi
AM_CONDITIONAL(USE_OPENBSD_MALLOC, test x$enable_openbsd_malloc = xyes)
-if test x$enable_instrument_downloads == xyes; then
+if test x$enable_instrument_downloads = xyes; then
AC_DEFINE(INSTRUMENT_DOWNLOADS, 1,
[Defined if we want to keep track of how much of each kind of resource we download.])
fi