RE: [Boost-users] Boost Logging Library 1.3 troubles

From: Ormond, Randy \(Mission Systems\) (Randy.Ormond_at_[hidden])
Date: 2005-06-02 12:31:55

Hi,
 
John Torjo's latest version (May 19) fixes my problems. Thanks again
John.
 
Randy 

  _____  

From: boost-users-bounces_at_[hidden]
[mailto:boost-users-bounces_at_[hidden]] On Behalf Of Ormond, Randy
(Mission Systems)
Sent: Wednesday, May 11, 2005 11:47 AM
To: boost-users_at_[hidden]
Subject: [Boost-users] Boost Logging Library 1.3 troubles

Hi,
 
If I'm following the threads correctly, it looks like John Torjo's
logging library may become an official part of Boost someday. It
certainly seems to be perfect for my needs.
 
But I'm having all sorts of trouble on Red Hat with gcc 3.2.2-5.  I had
to modify some source to avoid compile errors, which has me worried
given my lack of expertise.
 
In log.hpp, I had to change (sorry, I can't paste in code or compiler
output, this is typed in)
template<bool is_compile_time, bool is_enabled>
struct logger_keeper_is_enabled...
to
template<bool is_compile_time, bool is_enabledInput>
struct logger_keeper_is_enabled...
to avoid shadowing is_enabled
 
in ts_posix.hpp, I had to change the mutex ctr from
mutex() : m_mutex(0) {...
to
mutex() {...
This seems OK because m_mutex is initialized in the ctr body.
 
After making those changes, I tried the example in the basic_usage.html.
 
It hangs on the first call to BOOST_DEFINE_LOG.  I traced it with gdb to
find_log_by_name() at log_manager.cpp:294. From there, it goes to the
logger_info ctr. It hangs in lwm_pthreads.hpp:72 in the scoped_lock ctr,
apparently trying to get a lock.
 
Of course my mods to the source and general lack of insight have me
worried. I expect difficulties as an "early adopter" but any help would
be greatly appreciated. BTW, is anyone else trying to use this yet?
 
Thanks,
Randy