[
https://issues.apache.org/jira/browse/TS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644109#comment-13644109
]
ASF subversion and git services commented on TS-1732:
-----------------------------------------------------
Commit 854c6c18b524c749b437d18009e2b13c78cbc5ce in branch refs/heads/master
from [~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=854c6c1 ]
TS-1732 Do an ugly const_cast to work around an anomaly on Solaris.
On linux, this cast is a "no-op", since the struct option is sane
and the compile with convert it back to a const char*. Always doing
the const_cast avoids #ifdef's to maintain.
> Authproxy plugin doesn't compile on Solaris (or Illumos)
> --------------------------------------------------------
>
> Key: TS-1732
> URL: https://issues.apache.org/jira/browse/TS-1732
> Project: Traffic Server
> Issue Type: Bug
> Components: Build, Plugins
> Reporter: Igor Galić
> Assignee: Igor Galić
> Fix For: 3.3.1
>
>
> {noformat}
> gmake[2]: Entering directory
> `/home/i.galic/src/trafficserver/plugins/experimental/authproxy'
> CXX authproxy.lo
> authproxy.cc: In function 'TSEvent StateAuthProxyResolve(AuthRequestContext*,
> void*)':
> authproxy.cc:372:30: error: 'MAXHOSTNAMELEN' was not declared in this scope
> authproxy.cc:380:43: error: 'hostname' was not declared in this scope
> authproxy.cc: In function 'AuthOptions* AuthParseOptions(int, const char**)':
> authproxy.cc:715:5: error: deprecated conversion from string constant to
> 'char*' [-Werror=write-strings]
> authproxy.cc:715:5: error: deprecated conversion from string constant to
> 'char*' [-Werror=write-strings]
> authproxy.cc:715:5: error: deprecated conversion from string constant to
> 'char*' [-Werror=write-strings]
> authproxy.cc:715:5: error: deprecated conversion from string constant to
> 'char*' [-Werror=write-strings]
> cc1plus: all warnings being treated as errors
> gmake[2]: *** [authproxy.lo] Error 1
> {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
