[squid-dev] Build failed in Jenkins: 3.HEAD-amd64-FreeBSD-9.1 #799

Mon Nov 17 23:34:26 UTC 2014

See <http://build.squid-cache.org/job/3.HEAD-amd64-FreeBSD-9.1/799/changes>

Changes:

[Amos Jeffries] Fix output from squid.conf parser

DBG_CRITICAL level messages before self_destruct() require a FATAL: tag
to highlight the reason for the crash and obscure  "BUNGLED" text which
is about to follow.

[Amos Jeffries] Release Notes update for 3.6

[Amos Jeffries] Add squid.conf regression tests for 3.5

[Amos Jeffries] Fix delay_parameters parsing

Squid-3.4 parser changes resulted in always getting a BUNGLED error when
parsing delay_parameters. Convert to the new ConfigParser engine.

Add ability to specify 'none' for no-limit instead of -n/*

[Amos Jeffries] Cygwin: FOPEN may be defined

[Amos Jeffries] Fix segmentation fault in ACLUrlPathStrategy::match

CONNECT requests do not contain a path segment. If tested with a
urlpath_regex ACL will crash Squid via xstrdup() NULL protection.

[squidadm at squid-cache.org] SourceFormat Enforcement

[Christos Tsantilas] Adapting 100-continue

Currently squid fails to handle correctly "100 Continue" requests/responses
when ICAP is used. The problems discussed in squid bugzilla:
http://bugs.squid-cache.org/show_bug.cgi?id=4067

A short discussion of the problem:
When a data upload request enters squid (eg a PUT request with
"Expect: 100-continue" header), squid sends ICAP headers and HTTP headers to
ICAP server and stucks waiting for ever  the request body data.

This patch implements the "force_request_body_continuation" access list
directive which controls how Squid handles data upload requests from HTTP and
send the request body to Squid.
An allow match tells Squid to respond with the HTTP 100 or FTP 150
(Please Continue) control message on its own, before forwarding the
request to an adaptation service or peer. Such a response usually forces
the request sender to proceed with sending the body. A deny match tells
Squid to delay that control response until the origin server confirms
that the request body is needed. Delaying is the default behavior.

This is a Measurement Factory project

[Amos Jeffries] C++11: cleanup compiler flag detection logics

Annotate what GCC version is required to pass the -std=c++11 and
-std=c++0x feature detection tests.

Disable the tests for features we do not use that require GCC 4.5+.
This should allow Squid to continue building on older OS and compilers
at least until we start using those features.

[Amos Jeffries] RFC 6176 compliance

... prohibits use of SSLv2.
https://tools.ietf.org/html/rfc6176

Remove the documentation and support for configuring Squid with
SSLv2-only.

Explicitly enable the SSL_NO_SSLv2 option when provided by the library
to prevent implicit fallback.

Remove support for ssloptions= values which are for SSLv2-specific bugs.

Due to the way they are implemented with atoi() sslversion=N
configuration will still accept the values for SSLv2-only. But the
context creation will now unconditionally produce "SSLv2 not
supported" errors if the now undocumented values are attempted.

[Christos Tsantilas] Make helper queue size configurable patch: default queue size for external_acl fix

The default queue size value is never set for external_acl helpers.

[Christos Tsantilas] Make helper queue size configurable, with consistent defaults and better overflow handling.

This patch adds a queue-size=N option to helpers configuration. This
option allows users to configure the maximum number of queued requests
to busy helpers. We also adjusted the default queue size limits to be
more consistent across all helpers and made Squid more robust on some
queue overflows:

- external_acl helpers
Make the maximum queue size configurable via queue-size.
Default to 2*maximum-number-of-children.
If the queue overflows, then the ACL returns ACCESS_DUNNO.

Unpatched code uses the number of running children as the maximum
queue size. If the queue is overloaded, then the ACL returns ACCESS_DUNNO.

-redirector/storeID helpers
Make the maximum queue size configurable via queue-size.
Default to 2*maximum-number-of-children.
If the queue overflows and redirector_bypass configuration option
is set, then redirector is bypassed. Otherwise, if overloading
persists for more than 3 minutes squid quits with a FATAL message.
If the redirector_bypass/storeID_bypass is set then the default queue_size
is set to 0 for backward compatibility.

Unpatched code uses 2*number-of-running-children as the maximum queue size.
If the redirector_bypass/storeID_bypass is set then helper bypassed if all
of the children are busy.
If the queue is overloaded and redirector_bypass/storeID_bypass is not set
then squid quits with a FATAL message.

- ssl_crtd/ssl_crtd_validator helpers.
Make the maximum queue size configurable via queue-size.
Default to 2*maximum-number-of-children.
If the queue overflows, then helpers are bypassed. If overloading persists
for more than 3 minutes squid quits with a FATAL message.

The default size limit and overflow behavior has not changed.

- Authentication helpers
Make the maximum queue size configurable via queue-size.
Default to 2*maximum-number-of-children.
If the queue overflows and overloading persists for more than 3 minutes,
then squid quits with a FATAL message.

The default size limit and overflow behavior has not changed.

This is a Measurement Factory project

[Amos Jeffries] parserNG: add missing unit test for HTTP/0.9 case

[Christos Tsantilas] Parser-NG: fixes to allow ecap and ssl subsystems build

[Amos Jeffries] Parser-NG: adjust unit tests for new RFC compliance behaviour

Current parser in strict mode is complying with RFC 7230 removal of
completely empty lines (but not whitespace) before the request-line.

------------------------------------------
[...truncated 6421 lines...]
../../src/tests/testHttp1Parser.cc:846: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:860: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:861: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:862: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:863: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:864: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:865: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:866: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:867: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:868: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:869: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:870: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:871: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:872: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:873: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:874: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:875: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:884: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:885: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:886: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:887: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:888: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:889: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:890: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:891: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:892: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:893: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:894: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:895: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:896: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:897: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:898: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:899: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:958: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:959: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:960: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:961: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:962: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:963: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:964: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:965: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:966: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:967: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:968: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:969: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:970: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:971: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:972: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:973: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:996: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:997: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:998: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:999: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1000: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1001: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1002: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1003: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1004: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1005: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1006: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1007: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1008: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1009: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1010: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1011: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1025: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1026: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1027: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1028: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1029: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1030: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1031: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1032: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1033: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1034: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1035: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1036: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1037: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1038: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1039: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1040: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1070: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1071: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1072: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1073: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1074: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1075: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1076: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1077: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1078: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1079: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1080: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1081: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1082: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1083: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1084: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1085: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1117: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1118: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1119: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1120: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1121: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1122: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1123: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1124: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1125: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1126: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1127: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1128: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1129: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1130: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1131: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1132: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1145: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1146: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1147: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1148: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1149: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1150: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1151: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1152: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1153: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1154: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1155: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1156: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1157: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1158: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1159: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1160: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1191: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1192: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1193: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1194: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1195: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1196: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1197: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1198: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1199: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1200: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1201: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1202: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1203: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1204: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1205: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1206: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1218: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1219: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1220: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1221: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1222: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1223: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1224: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1225: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1226: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1227: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1228: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1229: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1230: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1231: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1232: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1233: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1244: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1245: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1246: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1247: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1248: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1249: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1250: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1251: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1252: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1253: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1254: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1255: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1256: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1257: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1258: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1259: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1270: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1271: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1272: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1273: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1274: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1275: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1276: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1277: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1278: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1279: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1280: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1281: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1282: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1283: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1284: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1285: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1298: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1299: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1300: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1301: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1302: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1303: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1304: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1305: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1306: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1307: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1308: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1309: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1310: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1311: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1312: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1313: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1326: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1327: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1328: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1329: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1330: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1331: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1332: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1333: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1334: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1335: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1336: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1337: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1338: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1339: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1340: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1341: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1377: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1378: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1379: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1380: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1381: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1382: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1383: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1384: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1385: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1386: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1387: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1388: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1389: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1390: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1391: error: expected primary-expression before '.' token
../../src/tests/testHttp1Parser.cc:1392: error: expected primary-expression before '.' token
*** [tests/testHttp1Parser.o] Error code 1
*** [check-am] Error code 1
*** [check-recursive] Error code 1
*** [check] Error code 1
*** [check-recursive] Error code 1
*** [distcheck] Error code 1
Build FAILED.
Build step 'Execute shell' marked build as failure