[
https://issues.apache.org/jira/browse/TS-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14102714#comment-14102714
]
Leif Hedstrom commented on TS-2095:
-----------------------------------
The last commit seems to have broken builds in various ways. I found at least
two different failures:
{code}
checking for boostlib >= 1.33... configure: We could not detect the boost
libraries (version 1.33 or higher). If you have a staged boost library (still
not installed) please specify $BOOST_ROOT in your environment and do not give a
PATH to --with-boost option. If you are sure you have boost installed, then
check your version number looking in <boost/version.hpp>. See
http://randspringer.de/boost for more documentation.
checking for library containing crypt... no
checking for pkg-config... /bin/pkg-config
checking whether compiling and linking against OpenSSL works... no
configure: error: failed to find OpenSSL
Build step 'Execute shell' marked build as failure
Warning: you have no plugins providing access control for builds, so falling
back to legacy behavior of permitting any downstream builds to be triggered
Finished: FAILURE
{code}
and
{code}
../../../../lib/ts/ink_inet.cc: In function 'hostent*
ink_gethostbyname_r(char*, ink_gethostbyname_r_data*)':
../../../../lib/ts/ink_inet.cc:61:52: error: cannot convert 'int*' to
'hostent**' for argument '5' to 'int gethostbyname_r(const char*, hostent*,
char*, size_t, hostent**, int*)'
&data->herrno);
{code}
In addition, also saw at least one case with a regression failure, but that
might be different?
> autoconf warnings related to unordered_map
> ------------------------------------------
>
> Key: TS-2095
> URL: https://issues.apache.org/jira/browse/TS-2095
> Project: Traffic Server
> Issue Type: Bug
> Components: Build
> Reporter: Leif Hedstrom
> Assignee: Bryan Call
> Fix For: 5.1.0
>
>
> {code}
> configure: WARNING: unordered_map: accepted by the compiler, rejected by the
> preprocessor!
> configure: WARNING: unordered_map: proceeding with the compiler's result
> checking for unordered_map... yes
> checking unordered_set usability... yes
> checking unordered_set presence... no
> configure: WARNING: unordered_set: accepted by the compiler, rejected by the
> preprocessor!
> configure: WARNING: unordered_set: proceeding with the compiler's result
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
