You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Arno Toell (JIRA)" <ji...@apache.org> on 2013/02/23 16:20:12 UTC

[jira] [Commented] (TS-1714) ATS 3.2 does not build with gcc 4.8 anymore

    [ https://issues.apache.org/jira/browse/TS-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585141#comment-13585141 ] 

Arno Toell commented on TS-1714:
--------------------------------

Debian did a gcc-4.8 rebuild as well now, so I can share more details on that matter. The rebuild revealed, a rebuild with -Werror=unused-result causes ATS to fail in TsErrataUtil.cc:

{code}
TsErrataUtil.cc: In function 'ts::Errata ts::msg::vlogf_errno(ts::Errata&, ts::Errata::Id, ts::Errata::Code, const char*, __va_list_tag (&)[1])':
TsErrataUtil.cc:143:36: error: ignoring return value of 'char* strerror_r(int, char*, size_t)', declared with attribute warn_unused_result [-Werror=unused-result]
     strerror_r(e, e_buffer, E_SIZE);
                                    ^
{code}

Full build log: http://people.debian.org/~doko/logs-20130217/gcc48/trafficserver_3.2.4-1_unstable_gcc48.log
Debian Bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701427
                
> ATS 3.2 does not build with gcc 4.8 anymore
> -------------------------------------------
>
>                 Key: TS-1714
>                 URL: https://issues.apache.org/jira/browse/TS-1714
>             Project: Traffic Server
>          Issue Type: Bug
>            Reporter: Arno Toell
>
> There is an upcoming tool chain update to gcc 4.8 which causes ATS not to build anymore from source. Personally I do not have gcc 4.8 yet, but Fedora people reported about issues during a mass rebuild of their packages: https://lists.fedoraproject.org/pipermail/devel/2013-January/175876.html
> Someone who has access to gcc 4.8 may give it a try and fix the problems. As it looks they're rather trivial. 

--
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