On Apr 14, 2008, at 8:39 AM, Chakravarthula, Krishnamurthy wrote:
Experts,
What is the compiler requirements for compiling log4cxx 0.10.0 on
different platforms?
Regards,
Krishna
That is a very open-ended question. The only out of date compilers
where compiler issues are coded around
On Apr 14, 2008, at 8:37 AM, Chakravarthula, Krishnamurthy wrote:
Experts,
When I am building log4cxx 0.10.0 on Solaris and I get the
following errors. Please advice.
[cc] __divdi30x174 ../
static/libapr-1.a(thread_cond.o)
[cc] __divdi3
On Apr 14, 2008, at 12:26 PM, J.T. Conklin wrote:
Hi,
When an appender's doAppend method throws an exception, it unwinds
through the call stack. At the very least, this means that the log
message won't be passed to any other appenders that might otherwise
process it. It seems to me that log4
Hi,
When an appender's doAppend method throws an exception, it unwinds
through the call stack. At the very least, this means that the log
message won't be passed to any other appenders that might otherwise
process it. It seems to me that log4cxx needs to protect calls to
doAppend with a try/catc
"Chakravarthula, Krishnamurthy" <[EMAIL PROTECTED]> writes:
> When I am building log4cxx 0.10.0 on Solaris and I get the
> following errors. Please advice.
I have managed to build log4cxx 0.10.0 on Solaris, but I have not
used maven or ant.
I downloaded apr and apt-util from http://apr.apac
Experts,
What is the compiler requirements for compiling log4cxx 0.10.0 on
different platforms?
Regards,
Krishna
Experts,
When I am building log4cxx 0.10.0 on Solaris and I get the following
errors. Please advice.
[cc] __divdi30x174
../static/libapr-1.a(thread_cond.o)
[cc] __divdi30x3c
../static/libapr-1.a(waitio.o)
[cc]
Hi Patrick,
You can do the same thing easier with log4cxx using environment variables.
Before initializing log4cxx, put your special folders into environment
variables:
char theDirectory[256];
char envVar[280];
determine application data dir
sprintf(envVar, "C
