Roland Bock wrote:
Hi,
good to see that boost.log is being formally reviewed! From what I read in the documentation so far, I am really looking forward to seeing the library included in boost.
I sure want to do some tests, hoping to replace our current logging system, soon, but today I can only answer the following review item:
- Did you try to use the library? With what compiler? Did you have any problems?
Yes, I tried and failed to compile it. Details are below.
Platform: Ubuntu 8.04, 64bit, g++ 4.2.4 Intel QuadCore 2.5GHz, 8GB Ram
Compilation: ============ Sounds embarassing, but I failed to compile the library. I copied the folders boost, lib and doc from boost-log-RC4 to boost_1_42_0, called ./bootstrap.sh ./bjam -d+2 --build-dir=build --with-log --prefix=/my/install/path link=shared runtime-link=shared install
All looked well until this point:
gcc.compile.c++ build/boost/bin.v2/libs/log/build/gcc-4.2.4/release/threading-multi/filter_parser.o
"g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -fno-strict-aliasing -DBOOST_ALL_NO_LIB=1 -DBOOST_DATE_TIME_DYN_LINK=1 -DBOOST_FILESYSTEM_DYN_LINK=1 -DBOOST_LOG_DLL -DBOOST_LOG_SETUP_BUILDING_THE_LIB=1 -DBOOST_LOG_SETUP_DLL -DBOOST_LOG_USE_NATIVE_SYSLOG=1 -DBOOST_SYSTEM_DYN_LINK=1 -DBOOST_THREAD_POSIX -DBOOST_THREAD_USE_DLL=1 -DDATE_TIME_INLINE -DNDEBUG -I"." -c -o "build/boost/bin.v2/libs/log/build/gcc-4.2.4/release/threading-multi/filter_parser.o"
"libs/log/src/filter_parser.cpp"
The process cc1plus was running about 20 minutes (100%CPU, moderate RAM usage) before anything else happened.
It looks like 4.2 is somehow unhappy with the code. Then, after lots and lots of very
long error messages, it continues like this:
...skipped <pbuild/boost/bin.v2/libs/log/build/gcc-4.2.4/release/threading-multi>libboost_log.so.1.42.0
for lack of <pbuild/boost/bin.v2/libs/log/build/gcc-4.2.4/release/threading-multi>attribute_set.o...
Hmm. Not sure how to proceed. Should I send the whole bunch of error messages to the list as an attachment?
I think you better locate the first error message from the compiler and post that. Further errors are likely induced. I wonder if the first error message is "ran out of memory", though. - Volodya