Fix a variable handling mistake when testing for libevent functions in configure.in. Found by Riastradh.

svn:r16793
This commit is contained in:
Nick Mathewson 2008-09-08 01:57:02 +00:00
parent baeb260ad1
commit 67327a863a
2 changed files with 3 additions and 1 deletions

View File

@ -8,6 +8,8 @@ Changes in version 0.2.1.6-alpha - 2008-09-xx
- Fixed some memory leaks --some quite frequent, some almost impossible - Fixed some memory leaks --some quite frequent, some almost impossible
to trigger-- based on results of a static analysis tool. (XXX Can we to trigger-- based on results of a static analysis tool. (XXX Can we
say which? -NM) say which? -NM)
- When testing for libevent functions, set the LDFLAGS variable
correctly. (Found by Riastradh.)
o Minor features: o Minor features:
- Use a lockfile to make sure that two Tor processes are not - Use a lockfile to make sure that two Tor processes are not

View File

@ -268,7 +268,7 @@ save_LIBS="$LIBS"
save_LDFLAGS="$LDFLAGS" save_LDFLAGS="$LDFLAGS"
save_CPPFLAGS="$CPPFLAGS" save_CPPFLAGS="$CPPFLAGS"
LIBS="-levent $TOR_LIB_WS32 $LIBS" LIBS="-levent $TOR_LIB_WS32 $LIBS"
LDFLAGS="$TOR_LDFLAGS_libevent $LIBS" LDFLAGS="$TOR_LDFLAGS_libevent $LDFLAGS"
CPPFLAGS="$TOR_CPPFLAGS_libevent $CPPFLAGS" CPPFLAGS="$TOR_CPPFLAGS_libevent $CPPFLAGS"
AC_CHECK_FUNCS(event_get_version event_get_method event_set_log_callback) AC_CHECK_FUNCS(event_get_version event_get_method event_set_log_callback)
LIBS="$save_LIBS" LIBS="$save_LIBS"