helaku created TS-1782:
--------------------------
Summary: CENTOS 5.8 x64 autoreconf fail
Key: TS-1782
URL: https://issues.apache.org/jira/browse/TS-1782
Project: Traffic Server
Issue Type: Bug
Components: Build
Reporter: helaku
[root@nbs35 trafficserver]# autoconf -i
configure.ac:43: error: possibly undefined macro: AM_INIT_AUTOMAKE
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.ac:50: error: possibly undefined macro: AC_DISABLE_STATIC
configure.ac:75: error: possibly undefined macro: dnl
configure.ac:154: error: possibly undefined macro: AC_MSG_RESULT
configure.ac:198: error: possibly undefined macro: AM_CONDITIONAL
configure.ac:516: error: possibly undefined macro: AC_MSG_NOTICE
configure.ac:548: error: possibly undefined macro: AM_PROG_AS
configure.ac:552: error: possibly undefined macro: AC_PROG_LIBTOOL
[root@nbs35 trafficserver]# cat /etc/redhat-release
CentOS release 5.8 (Final)
2.6.18-308.11.1.el5 #1 SMP Tue Jul 10 08:48:43 EDT 2012 x86_64 x86_64 x86_64
GNU/Linux
[root@nbs35 trafficserver]# git show
commit 4e53792f2740de507b6fd51f0d34f6bf4f780852
Author: Igor Gali[7m<87> <[email protected]>
Date: Wed Mar 27 00:47:21 2013 +0100
TS-1781: Make clang happy and esi compile
diff --git a/plugins/experimental/esi/lib/EsiProcessor.cc
b/plugins/experimental/esi/lib/EsiProcessor.cc
index ed4868b..96a647e 100644
--- a/plugins/experimental/esi/lib/EsiProcessor.cc
+++ b/plugins/experimental/esi/lib/EsiProcessor.cc
@@ -422,7 +422,7 @@ EsiProcessor::flush(string &data, int &overall_len) {
const Attribute &url = (*node_iter).attr_list.front();
string raw_url(url.value, url.value_len);
attemptUrls.push_back(_expression.expand(raw_url));
- if (!_getIncludeStatus(*node_iter) == STATUS_ERROR) {
+ if (_getIncludeStatus(*node_iter) != STATUS_DATA_AVAILABLE) {
attempt_succeeded = false;
_errorLog("[%s] attempt section errored; due to url [%s]",
__FUNCTION__, raw_url.c_str());
break;
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
