Re: [Boost-testing] [EXTERNAL] develop regression shunted with process_jam_log build failure

Subject: Re: [Boost-testing] [EXTERNAL] develop regression shunted with process_jam_log build failure
From: Belcourt, Kenneth (kbelco_at_[hidden])
Date: 2014-02-05 23:13:16

On Feb 5, 2014, at 3:50 PM, Jim Bell wrote:

> On 2014-02-03 11:52 PM, Belcourt, Kenneth wrote:
>> On Feb 3, 2014, at 12:58 PM, Jim Bell wrote:
>> 
>>> process_jam_log build fails on the develop side (which shunts the regression), with:
>>> 
>>> ../../../boost/smart_ptr/detail/array_deleter.hpp: In member function ‘void boost::detail::array_deleter<T>::init(boost::detail::array_deleter<T>::type*)’:
>>> ../../../boost/smart_ptr/detail/array_deleter.hpp:60:36: error: ‘count’ was not declared in this scope
>>> array_init(memory, count);
>>> 
>>> Any objection to using the process_jam_log built on the master side?
>> 
>> Strange, is code the above in the develop branch, I can't find it?   Maybe it's out of date, here's what I've got for array_deleter.hpp.
> 
> Please forgive my incomplete post. Full messages below. Both process_jam_log.cpp and tiny_xml.cpp hit the same cascade of errors. This is Linux (OpenSUSE), gcc-4.8.
> 
> gcc.compile.c++ bin/gcc-4.8/release/process_jam_log.o
> 
> "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_FILESYSTEM_STATIC_LINK=1 -DBOOST_SYSTEM_STATIC_LINK=1 -DNDEBUG -D_CRT_SECURE_NO_WARNINGS -I"../../.." -c -o "bin/gcc-4.8/release/process_jam_log.o" "../src/process_jam_log.cpp"

Strange, here's mine on RHEL 6.3 (Santiago).

gcc.compile.c++ bin/gcc-4.8.2/release/process_jam_log.o

    "g++"  -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -fPIC  -DBOOST_ALL_NO_LIB=1 -DBOOST_FILESYSTEM_STATIC_LINK=1 -DBOOST_SYSTEM_STATIC_LINK=1 -DNDEBUG -D_CRT_SECURE_NO_WARNINGS  -I"../../.." -c -o "bin/gcc-4.8.2/release/process_jam_log.o" "../src/process_jam_log.cpp"

Seems to compile fine.  Is this a known issue with gcc-4.8, maybe fixed by patch release 4.8.2?

-- Noel