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 2011/06/14 23:10:55 UTC

[jira] [Updated] (TS-840) Regression checks fail (again) due to faulty assert use

     [ https://issues.apache.org/jira/browse/TS-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arno Toell updated TS-840:
--------------------------

    Attachment: ink_assert.patch

> Regression checks fail (again) due to faulty assert use
> -------------------------------------------------------
>
>                 Key: TS-840
>                 URL: https://issues.apache.org/jira/browse/TS-840
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 3.0.0
>            Reporter: Arno Toell
>            Priority: Minor
>         Attachments: ink_assert.patch
>
>
> When trying to compile regression checks, they fail again for ATS 3.0. They were fixed in TS-738 some time ago, but are now failing again, this time because of a build failure. Problem is the usage of _assert()_:
> {code}
> libtool: link: g++ -g -O2 -pipe -Wall -Werror -O3 -feliminate-unused-debug-symbols -fno-strict-aliasing -Wno-invalid-offsetof -o .libs/test_Map test_Map.o  ./.libs/libtsutil.so -L/usr/lib -lpcre -lssl -lcrypto -ltcl8.4 -lresolv -lrt -lnsl -lcap -lz -Wl,-rpath -Wl,/usr/lib/trafficserver
> g++ -DHAVE_CONFIG_H -I.   -D_LARGEFILE64_SOURCE=1 -D_COMPILE64BIT_SOURCE=1 -D_GNU_SOURCE -D_REENTRANT -Dlinux -I/usr/include/tcl8.4  -g -O2 -pipe -Wall -Werror -O3 -feliminate-unused-debug-symbols -fno-strict-aliasing -Wno-invalid-offsetof -c -o test_Vec.o test_Vec.cc
> test_Vec.cc: In function 'int main(int, char**)':
> test_Vec.cc:38: error: '__DONT_USE_BARE_assert_USE_ink_assert__' was not declared in this scope
> {code}
> This is due to following definition in _lib/ts/ink_assert.h_:
> {code}
> #undef assert
> #define assert __DONT_USE_BARE_assert_USE_ink_assert__
> {code}
> I attached a patch which is fixing this issue. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira