[
https://issues.apache.org/jira/browse/TS-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Peach resolved TS-1688.
-----------------------------
Resolution: Fixed
Fix Version/s: 3.3.1
Assignee: Igor Galić
> TsConfig doesn't build on OmniOS/gcc-4.7
> ----------------------------------------
>
> Key: TS-1688
> URL: https://issues.apache.org/jira/browse/TS-1688
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration
> Reporter: Igor Galić
> Assignee: Igor Galić
> Fix For: 3.3.1
>
>
> {noformat}
> gmake[3]: Entering directory `/home/i.galic/src/trafficserver/lib/tsconfig'
> /bin/sh ../../libtool --tag=CXX --mode=compile g++ -m64 -DHAVE_CONFIG_H
> -I. -I../../lib/ts -I../../lib -I../../lib/ts -D_LARGEFILE64_SOURCE=1
> -D_COMPILE64BIT_SOURCE=1 -D_GNU_SOURCE -D_REENTRANT -Dsolaris
> -I/opt/omni/include/amd64 -std=c++11 -g -pipe -Wall -Werror -O3
> -feliminate-unused-debug-symbols -fno-strict-aliasing -Wno-invalid-offsetof
> -MT TsBuilder.lo -MD -MP -MF .deps/TsBuilder.Tpo -c -o TsBuilder.lo
> TsBuilder.cc
> libtool: compile: g++ -m64 -DHAVE_CONFIG_H -I. -I../../lib/ts -I../../lib
> -I../../lib/ts -D_LARGEFILE64_SOURCE=1 -D_COMPILE64BIT_SOURCE=1 -D_GNU_SOURCE
> -D_REENTRANT -Dsolaris -I/opt/omni/include/amd64 -std=c++11 -g -pipe -Wall
> -Werror -O3 -feliminate-unused-debug-symbols -fno-strict-aliasing
> -Wno-invalid-offsetof -MT TsBuilder.lo -MD -MP -MF .deps/TsBuilder.Tpo -c
> TsBuilder.cc -fPIC -DPIC -o .libs/TsBuilder.o
> In file included from TsBuilder.h:27:0,
> from TsBuilder.cc:24:
> TsValue.h: In member function 'ts::config::Value
> ts::config::Value::operator[](const char*) const':
> TsValue.h:682:104: error: 'strlen' was not declared in this scope
> TsValue.h: In member function 'ts::config::Value
> ts::config::Value::find(const char*)':
> TsValue.h:687:93: error: 'strlen' was not declared in this scope
> gmake[3]: *** [TsBuilder.lo] Error 1
> gmake[3]: Leaving directory `/home/i.galic/src/trafficserver/lib/tsconfig'
> {noformat}
--
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
