, it compiles the dynamic library and the two examples. In
the future, I will add more features.
Bernard.
--
Dr. Sven A. Schmidt
abstracture IT-Beratung GmbH mail: [EMAIL PROTECTED]
Obere Kirchstr. 7fon: +49 6123 704 79 57
65344 Eltville fax: +49 6123 704 79 61
Bill,
there's nothing you can do influence the order of global static
initialization. It can go wrong any time it pleases. I found that
callig doConfigure (or similar) gets the initialization done (see my
previous posts about two months ago).
HTH,
Sven
On 21.10.2004, at 04:20, Xiong, Wei (Wei)
This might be unrelated, but I've had loads of trouble with linking
STL/template code on Solaris. Using the compiler switch
-instances=static fixed all my problems. Found here:
http://hunnysoft.com/support/forum/messages/2019.htm
HTH,
Sven
On 31.08.2004, at 19:42, Surekha Guntur wrote:
When I reported this problem a few days ago (Re: Building on Mac OS/X
10.3) I thought this was a platform specific problem... This doesn't
seem to be the case after all. Even the included example delayedloop
relies on static initialization (like in your fred) and crashes right
away.
IMHO,
On 27.08.2004, at 12:36, Stoyan Damov wrote:
Yes Tom, thanks. I suspect that too, I was just making a point that one
should follow the API docs and common C++ sense instead of ranting ;)
Well, I didn't intend to rant... The API docs on
http://logging.apache.org/log4cxx/manual/Introduction.html
On 27.08.2004, at 13:26, Stoyan Damov wrote:
OK, sorry if it seems that I attacked you :) I'm not connected to the
log4cxx project in any other way than being a satisified user :)
No hard feelings on this end of the wire :)
Cheers,
Sven
Hi all,
I've just downloaded and compiled the latest release (0.9.7) on OSX
10.3. I've seen the same problems and found that the getLogger() and
getRootLogger() calls cause segfaults unless I call
BasicConfigurator::configure();
first. So, for example delayedloop can be fixed like this:
int
