log4cpp-devel — technical discussions about the development of log4cpp

[Log4cpp-devel] integration of Boost libraries

[Bastiaan B. <Bas...@li...>]

Hi,
=20
For release 0.3.0 I'd like to address two issues:
1) multithreading support.
2) object ownership: share Appenders, Layouts, Filters, etc. between =
multiple Categories and Appenders without having to worry about memory =
management.
=20
Regarding multithreading support, several people have pointed me to the =
Boost threading library (see www.boost.org) for portable MT support.
For addressing the second issue Boost also seems to provide the =
necessary code, in the form of its shared pointers.
So, barring any convincing arguments against using Boost, it will a =
dependency of 0.3.0 and upwards.
=20
Since I have no experience with Boost yet, I'm very open to suggestions =
or help on how to integrate Boost in log4cpp. The Boost people recommend =
to simply dump the Boost headers files your project needs in a boost =
subdirecty within your project. This has the distinct advantage of not =
requiring people to have Boost installed. However, if people already use =
Boost in their projects the version in log4cpp may conflict with it.=20
Does anyone have a nice setup to handle this from autoconf, e.g. =
'--with-boost=3D'?=20
=20
Thanks,
=20
Bastiaan
=20
=20
=20

RE: [Log4cpp-devel] Port to BCB

[Bastiaan B. <Bas...@li...>]

Hi Uwe,

Thanks for checking the BCB port. With Linux, Solaris, MSVC++ and BCB =
checked, I think 0.2.7 is ready.

The STDOUT_FILENO problem was already reported in bug #506907 and fixed =
in rc2 (with fileno(), just like your fix). Unfortunately I failed to =
notice that I hadn't comitted it to CVS yet. Sorry for the duplication =
of work!=20

Cheers,

Bastiaan


> -----Original Message-----
> From: Uwe J=E4ger [mailto:ja...@va...]
> Sent: Friday, January 25, 2002 9:56 AM
> To: log...@li...
> Subject: [Log4cpp-devel] Port to BCB
>=20
>=20
> Hi,
>=20
> I checked my platform and had to changes to make:
> BCB didn't know STDOUT_FILENO and STDERR_FILENO, so I=20
> replaced them with
> fileno(stdout) and fileno(stderr). I think this should work=20
> on the other=20
> platforms too. There was another small issue in a test program, I=20
> replaced a ?-: operator with an if statement because there was some=20
> confussion about the types (char* and std:string) which my compiler=20
> didn't like.
>=20
> Ciao
> Uwe
>=20
>=20
> _______________________________________________
> Log4cpp-devel mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4cpp-devel
>=20

[Log4cpp-devel] Port to BCB

[Uwe <ja...@va...>]

Hi,

I checked my platform and had to changes to make:
BCB didn't know STDOUT_FILENO and STDERR_FILENO, so I replaced them with
fileno(stdout) and fileno(stderr). I think this should work on the other 
platforms too. There was another small issue in a test program, I 
replaced a ?-: operator with an if statement because there was some 
confussion about the types (char* and std:string) which my compiler 
didn't like.

Ciao
Uwe

[Log4cpp-devel] 0.2.7 RC1 released

[Bastiaan B. <Bas...@li...>]

Hi,
=20
Last night I put release 0.2.7 RC1 on SourceForge. I'll rename it to =
0.2.7 next monday if noone finds urgent problems. Because the SF release =
pages have broken down again I couldn't add release notes or a =
changelog, so I'll give the changes versus 0.2.6b here:
=20
Support for multiple Appenders per Category added (feature request =
#501360).
Fixed variable scope bug in SyslogAppender (bug #499315)
Fixed memory leak in SyslogAppender and RemoteSyslogAppender (bug =
#499524)
Fixed compile problem in Filter (bug #)
Fixed config file parse problem in SimpleConfigurator (bug #500766)
Added methods for logging at FATAL level (bug #504314)

Please check whether RC1 is OK on your platform, as usual I've only =
checked Linux RH7.2 x86.
=20
Cheers,
=20
Bastiaan
=20

[Log4cpp-devel] Added support for multiple appenders per category

[Bastiaan B. <bas...@li...>]

Hi all,

Brendan B. Boerner has contributed support for attaching multiple 
Appenders to Categories. His patch has been merged now and I intend to 
ship it with release 0.2.7 as it should not break compatibility with the 
existing interface. Please check and scream or fix if we've missed 
something.
NB. SimpleConfigurator has not been updated to support multiple 
Appenders yet. If you have time to work on that please go ahead.

Cheers,

Bastiaan
 

Re: [Log4cpp-devel] [off topic] First log4c release

[Bastiaan B. <bas...@li...>]

Cedric Le Goater wrote:

>Hi all,
>
>This is a bit off topic for a log4cpp mailing list.
>
>I use to work on log4cpp a year ago but I've been quite passive for a
>while. My contribution was small but I learned a lot from Bastiaan and all
>of you. 
>
Thanks. But don't diminish your contribution, your autoconf setup was a 
large step forward for building and packaging log4cpp.

>
>Since, I changed work and I had to come back to good old C language. No
>more C++, no more log4cpp and log4c didn't exist. So, I gave it a try and
>released an initial version of log4c on freshmeat. A lot of the ideas
>behind log4c come from log4cpp, even the documentation is similar (Excuse
>my lazyness :-).
>
Were do you think most of log4cpp documentation comes from? ;-)
Credits go to Ceki and friends.

>
>If the log4c project has some future, I think some parts could be merged
>with log4cpp. There's a lot of work to do before it reaches log4cpp
>quality and portability, but C being more portable than C++, it shouldn't
>be to hard.
>
>log4c can be found here :
>	
>	http://www.cimai.com/opensource/log4c/log4c-1.0.2.tar.gz
>
>C.
>
Congrats on your log4c release! The log4* family gets larger and 
larger... :-)

Bastiaan

[Log4cpp-devel] [off topic] First log4c release

[Cedric Le G. <leg...@fr...>]

Hi all,

This is a bit off topic for a log4cpp mailing list.

I use to work on log4cpp a year ago but I've been quite passive for a
while. My contribution was small but I learned a lot from Bastiaan and all
of you. 

Since, I changed work and I had to come back to good old C language. No
more C++, no more log4cpp and log4c didn't exist. So, I gave it a try and
released an initial version of log4c on freshmeat. A lot of the ideas
behind log4c come from log4cpp, even the documentation is similar (Excuse
my lazyness :-).

If the log4c project has some future, I think some parts could be merged
with log4cpp. There's a lot of work to do before it reaches log4cpp
quality and portability, but C being more portable than C++, it shouldn't
be to hard.

log4c can be found here :
	
	http://www.cimai.com/opensource/log4c/log4c-1.0.2.tar.gz

C.

FW: [Log4cpp-devel] Daily Rolling File Appender v3

[Bastiaan B. <Bas...@li...>]

=20
-----Original Message-----
From: Alex Tapaccos [mailto:ATa...@re...]
Sent: Thursday, January 10, 2002 11:10 AM
To: 'log...@li...'
Subject: RE: [Log4cpp-devel] Daily Rolling File Appender v3



Thanks to Evert for all his useful comments=20
Event  it looks like we are both right the Log4j equivalent is called
DailyRollingFileAppender!=20
I have renamed the files accordingly plus added some extra time checks
for each duration.=20

The config file option will now have to say=20
appender category         layout  dailyrolling lognameformat frequency=20

e.g.=20
appender Test.Application pattern dailyrolling %d%m%Y.log hourly %r %c
%p %m%n=20

I am glad it compiles with Borland as I use VC but tried to stick within
the STL.=20

Test App=20

// LogTest.cpp : Defines the entry point for the console application.=20
//=20

#include "stdafx.h"=20

#include "RFStringTable.h"=20
#include <stdio.h>=20
#include "conio.h"=20
#include "windows.h"=20
#include <iostream>=20
#include "log4cpp/Category.hh"=20
#include "log4cpp/Appender.hh"=20
#include "log4cpp/OstreamAppender.hh"=20
#include "log4cpp/Layout.hh"=20
#include "log4cpp/BasicLayout.hh"=20
#include "log4cpp/Priority.hh"=20
#include "log4cpp/NDC.hh"=20
#include "log4cpp/SimpleConfigurator.hh"=20
#include "windows.h"=20
#include "process.h"=20
#include "conio.h"=20



int main(int argc, char* argv[])=20
{=20
        try=20
        {=20
                log4cpp::SimpleConfigurator::configure("your config
file");=20

                log4cpp::Category& sub1=3D=20
        log4cpp::Category::getInstance(std::string("Test.Application"));

                sub1.error("FOO");=20
               =20
                while (1)  // This loop will allow to keep add messages
while changing your clock for testing=20
                {=20
                        if (_kbhit())=20
                        {=20
                                char t=3Dgetch();=20
                                if (t=3D=3D'q') break; =20
                                sub1.error("BAR");=20
                                t=3D0;=20
                        }=20
                }=20
        }=20
        catch (log4cpp::ConfigureFailure& e)=20
        {=20
                printf(e.what());=20

        }=20
        log4cpp::Category::shutdown();=20
        return 0;=20
}=20

RE: [Log4cpp-devel] Rolling File Appender v2

[Bastiaan B. <Bas...@li...>]

Hi,

Alex, thanks for the contribution!
I've committed RollingFileAppender to CVS. Made a slight change to get
it to compile on Linux:=20
modified the lines with strtup() to compare using strcasecmp(), because
strtup() is not portable. Yes, neither is strcasecmp() but (at least?)
Win32 has an equivalent in the form of stricmp(). This will be fixed in
Portability.hh. After that the Win32 project files can be updated and
the SimpleConfigurator patch applied.
Also the class needs (Doxygen) documentation, paritcularly since its use
is limited to non forking programs. And until log4cpp has proper
multithreading support limited to single threading programs as well.=20
To be honest, on *nix systems I think it's much simpler to let
logrotated handle the rolling of log files. Then the daemon only needs
to let the Appenders reopen the logfiles upon recieving a HUP signal.

  =20
> -----Original Message-----
> From: Evert Haasdijk [mailto:ev...@zu...]
> Sent: Thursday, January 10, 2002 9:16 AM
> To: Alex Tapaccos; log...@li...
> Subject: RE: [Log4cpp-devel] Rolling File Appender v2
>=20
>=20
> Alex,
>=20
> Maybe I'm picking nits here, but in log4j the RollingFileAppender is
> different: it just rolls over when it reaches a certain=20
> maximum size. What
> you've made looks more like their DailyFileAppender. Maybe=20
> you should rename
> it?
>

Hmm, yes, apparently the log4j folks associate rolling primarily with
size whereas Alex and I first think of time. Therefore I already
committed the Appender before noticing the different name in log4j. I do
agree however that it's better to have the same names in both log4j and
log4cpp to avoid confusion. I'll rename it....
=20
=20
> Otherwise, it compiles with Borland C++ Builder - if you have a test
> program, I'll test that it actually works with the Builder, too.
>

Yes, a small test program for in $topdir/tests would be nice.=20

Thanks,

Bastiaan
=20
> Ta, Evert

RE: [Log4cpp-devel] Rolling File Appender v2

[Evert H. <ev...@zu...>]

Alex,

Maybe I'm picking nits here, but in log4j the RollingFileAppender is
different: it just rolls over when it reaches a certain maximum size. What
you've made looks more like their DailyFileAppender. Maybe you should rename
it?

Otherwise, it compiles with Borland C++ Builder - if you have a test
program, I'll test that it actually works with the Builder, too.

Ta, Evert

-----Original Message-----
From: log...@li...
[mailto:log...@li...]On Behalf Of Alex Tapaccos
Sent: Wednesday, January 09, 2002 16:27 PM
To: 'log...@li...'
Subject: [Log4cpp-devel] Rolling File Appender v2


How to make a fool of one'self
Here are the correct files


-----Original Message-----
From: Alex Tapaccos [mailto:ATa...@re...]
Sent: 09 January 2002 15:24
To: 'log...@li...'
Subject: [Log4cpp-devel] Rolling File Appender


Dear All
Here is my first attempt for a rolling file appender so that log files can
change on specified periods
<<RollingFileAppender.cpp>> <<RemoteSyslogAppender.hh>>
These lines need to be added to the simpleconfigurator
else if (appenderName.compare("rolling") == 0)

        std::string logFileNameFormat;
        std::string rollingDuration;
            if (!(initFile >> logFileNameFormat))

                throw ConfigureFailure("Missing filename for rolling log
file format logging configuration file for category: " + categoryName);
        }
        if (!(initFile >> rollingDuration))

                throw ConfigureFailure("Missing duration for rolling log
file format logging configuration file for category: " + categoryName);
            }
        appender = new log4cpp::RollingFileAppender(categoryName,
logFileNameFormat,RollingFileAppender::getDuration(rollingDuration));
            }


Features
1. Hourly,daily,weekly,monthly changes
2. Allows you to specify format of file name, uses the method strftime to
achieve this
3. Can be accessed by the simple configurator by using following syntax
        appender Category pattern rolling %d%m%Y.log hourly %r %c %p %m%n
                                    ^            ^                     ^ how
often to change file
                                        |             name of log to
generate this example 09012002.log
                                    |
                                   appender name




Apologies for any bugs!!!
Look forward to comments
Regards
Alex

RE: [Log4cpp-devel] DOMConfigurator

[Bastiaan B. <Bas...@li...>]

> -----Original Message-----
> From: Evert Haasdijk [mailto:ev...@zu...]
> Sent: Wednesday, January 09, 2002 5:28 PM
> To: log...@li...
> Subject: [Log4cpp-devel] DOMConfigurator
>=20
>=20
> Hi all,
>=20
> Is anybody working on a DOMConfigurator? Is anybody=20

AFAIK noone is...

> interested in having
> one? I'm thinking about creating one (using xerces-c for DOM=20
> handling) to

I am, I am! :-)

> get acquainted (sp?) with log4cpp, but if no-one's=20
> interested, I'll try my

> hand on something else (suggestions welcome).
>=20
> Ta, Evert
>=20

I like to talk more about this, but have to go to a meeting now :-(

Good luck,

Bastiaan

[Log4cpp-devel] DOMConfigurator

[Evert H. <ev...@zu...>]

Hi all,

Is anybody working on a DOMConfigurator? Is anybody interested in having
one? I'm thinking about creating one (using xerces-c for DOM handling) to
get acquainted (sp?) with log4cpp, but if no-one's interested, I'll try my
hand on something else (suggestions welcome).

Ta, Evert

Re: [Log4cpp-devel] Compiling with C++Builder 5

[Uwe <ja...@va...>]

Hi,

The __int64 is there, and the ostream operator, too. So the following
gives you the int64_t and the build in operator.

#ifndef LOG4CPP_HAVE_INT64_T
#define LOG4CPP_HAVE_INT64_T
#define int64_t __int64
#ifndef __BORLANDC__
#define LOG4CPP_MISSING_INT64_OSTREAM_OP
#endif
#endif

I made other minor changes for the port and might be able to commit them
  some time next week.

Ciao
Uwe

Bastiaan Bakker wrote:

> Hi David,
> 
> Thanks for the info, but could you give some more details about your 
> compilation problems? Borland C++ Builder  in fact does seem to have a 
> '__int64' type, and one would prefer to use it instead of a 'double' if 
> possible.
> 
> Regards,
> 
> Bastiaan
> 
> 
> David Robison wrote:
> 
>> I had a problem compiling with Borland C++ builder 5. I opened the 
>> Project
>> file in the bcb5 directory but it would not compile correctly. I had to
>> modify the config-win32.h file to place the conditional
>>
>> #ifndef __BORLANDC__
>>
>> around the following code
>>
>>
>> /* define if the compiler has int64_t */
>> #ifndef __BORLANDC__
>> #ifndef LOG4CPP_HAVE_INT64_T
>> #define LOG4CPP_HAVE_INT64_T
>> #define int64_t __int64
>> #define LOG4CPP_MISSING_INT64_OSTREAM_OP
>> #endif
>> #endif
>>
>> I did this and then it compiled normally. I hope this helps
>>
>> David Robison
>>
>>
>> _______________________________________________
>> Log4cpp-devel mailing list
>> Log...@li...
>> https://lists.sourceforge.net/lists/listinfo/log4cpp-devel
>>
> 
> 
> 
> 
> _______________________________________________
> Log4cpp-devel mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4cpp-devel

Re: [Log4cpp-devel] Compiling with C++Builder 5

[Bastiaan B. <bas...@li...>]

Hi David,

Thanks for the info, but could you give some more details about your 
compilation problems? Borland C++ Builder  in fact does seem to have a 
'__int64' type, and one would prefer to use it instead of a 'double' if 
possible.

Regards,

Bastiaan


David Robison wrote:

>I had a problem compiling with Borland C++ builder 5. I opened the Project
>file in the bcb5 directory but it would not compile correctly. I had to
>modify the config-win32.h file to place the conditional
>
>#ifndef __BORLANDC__
>
>around the following code
>
>
>/* define if the compiler has int64_t */
>#ifndef __BORLANDC__
>#ifndef LOG4CPP_HAVE_INT64_T
>#define LOG4CPP_HAVE_INT64_T
>#define int64_t __int64
>#define LOG4CPP_MISSING_INT64_OSTREAM_OP
>#endif
>#endif
>
>I did this and then it compiled normally. I hope this helps
>
>David Robison
>
>
>_______________________________________________
>Log4cpp-devel mailing list
>Log...@li...
>https://lists.sourceforge.net/lists/listinfo/log4cpp-devel
>

[Log4cpp-devel] Compiling with C++Builder 5

[David R. <drr...@op...>]

I had a problem compiling with Borland C++ builder 5. I opened the Project
file in the bcb5 directory but it would not compile correctly. I had to
modify the config-win32.h file to place the conditional

#ifndef __BORLANDC__

around the following code


/* define if the compiler has int64_t */
#ifndef __BORLANDC__
#ifndef LOG4CPP_HAVE_INT64_T
#define LOG4CPP_HAVE_INT64_T
#define int64_t __int64
#define LOG4CPP_MISSING_INT64_OSTREAM_OP
#endif
#endif

I did this and then it compiled normally. I hope this helps

David Robison

[Log4cpp-devel] 0.2.6 RC 4: Made Log4cppCleanup conditional

[Bastiaan B. <Bas...@li...>]

Hi all,
=20
Testing of 0.2.6RC3 on Solaris8 + gcc 2.95.3, resulted in failures for
'make distcheck', when enabling shared libraries. They are cause by the
cleanup in Log4cppCleanup. Since I like to get rid of this class in
0.3.0 anyway and on most (all?) supported platforms the closing sockets,
files, etc. isn't actually necessary I made the use of this class
conditional.=20
If you want to use the cleanup class you now have to #define
LOG4CPP_USE_CLEANUP. The default for this flag is off, which of course
is a change from RC3 and earlier.
=20
Regards,
=20
Bastiaan
=20

RE: [Log4cpp-devel] 0.2.6 final release pending: please check your platforms

[Bastiaan B. <Bas...@li...>]

Hi Uwe,

Still having problems? Are you using cvs.log4cpp.sourceforge.net ( =3D
usw-pr-cvs.sourceforge.net =3D 216.136.171.202).=20
On my RH Linux 7.2 box, I don't get a connect refused, but either the
local or remote ssh has problems with closing the connection. Don't know
why yet...

Anyway, if you can't access CVS, please try the release and diff against
that if it needs patching. I'll be happy to merge your fixes.

Regards,

Bastiaan

PS. I'll release RC4 in the coming hour, you may want to wait for that.
=20

> -----Original Message-----
> From: Uwe J=E4ger [mailto:ja...@va...]
> Sent: Tuesday, December 04, 2001 1:33 PM
> To: log...@li...
> Cc: Bastiaan Bakker
> Subject: Re: [Log4cpp-devel] 0.2.6 final release pending: please check
> your platforms
>=20
>=20
> I'd love to, but I have troubles updating my working copy,
> "Secure connection to ... refused". Anybody experiencing similar
> problens?
>=20
> Ciao
> Uwe
>=20
> Bastiaan Bakker wrote:
>=20
> > Hi all,
> >=20
> > =20
> >=20
> > Last night I uploaded 0.2.6 release candidate 3. This=20
> candidate replaces=20
> > Cedrics alternative snprintf() with the one at=20
> > http://www.ijs.si/software/snprintf/ , which I expect to be more=20
> > portable. Also some preliminary support for the OpenVMS=20
> platform has=20
> > been added. Tony Cheung has joined the project to maintain=20
> log4cpp for=20
> > OpenVMS.
> >=20
> > =20
> >=20
> > With the snprintf() update my todo list for 0.2.6 has been=20
> completed.=20
> > If no breakage of previously supported platforms is reported I'll=20
> > relabel it 0.2.6 final. I'll be on holiday next week, so=20
> you'll have=20
> > time until monday December the 10th to fix or report any=20
> problems or an=20
> > "OK".
> >=20
> > =20
> >=20
> > Cheers,
> >=20
> > =20
> >=20
> > Bastiaan
> >=20
> > =20
> >=20
>=20
>=20
>=20

Re: [Log4cpp-devel] 0.2.6 final release pending: please check your platforms

[Uwe <ja...@va...>]

I'd love to, but I have troubles updating my working copy,
"Secure connection to ... refused". Anybody experiencing similar
problens?

Ciao
Uwe

Bastiaan Bakker wrote:

> Hi all,
> 
>  
> 
> Last night I uploaded 0.2.6 release candidate 3. This candidate replaces 
> Cedrics alternative snprintf() with the one at 
> http://www.ijs.si/software/snprintf/ , which I expect to be more 
> portable. Also some preliminary support for the OpenVMS platform has 
> been added. Tony Cheung has joined the project to maintain log4cpp for 
> OpenVMS.
> 
>  
> 
> With the snprintf() update my todo list for 0.2.6 has been completed. 
> If no breakage of previously supported platforms is reported I'll 
> relabel it 0.2.6 final. I'll be on holiday next week, so you'll have 
> time until monday December the 10th to fix or report any problems or an 
> "OK".
> 
>  
> 
> Cheers,
> 
>  
> 
> Bastiaan
> 
>  
> 

[Log4cpp-devel] 0.2.6 final release pending: please check your platforms

[Bastiaan B. <Bas...@li...>]

Hi all,
=20
Last night I uploaded 0.2.6 release candidate 3. This candidate replaces
Cedrics alternative snprintf() with the one at
http://www.ijs.si/software/snprintf/ , which I expect to be more
portable. Also some preliminary support for the OpenVMS platform has
been added. Tony Cheung has joined the project to maintain log4cpp for
OpenVMS.
=20
With the snprintf() update my todo list for 0.2.6 has been completed. If
no breakage of previously supported platforms is reported I'll relabel
it 0.2.6 final. I'll be on holiday next week, so you'll have time until
monday December the 10th to fix or report any problems or an "OK".=20
=20
Cheers,
=20
Bastiaan
=20

[Log4cpp-devel] microsecond precision timestamps in release 0.2.6

[Bastiaan B. <Bas...@li...>]

Hi everybody,
=20
After many requests for more precise timestamps I've added a 'TimeStamp'
class to replace the 'time_t' field in LoggingEvent. It has microsecond
precision on platforms that have gettimeofday(), millisecond precision
on platforms with ftime() and second precision on all others, using
time().=20
If noone has serious objections I'll include the change in 0.2.6 as it
won't afffect the average user who doesn't write his/her own Appenders.
=20
Regards,
=20
Bastiaan
=20
PS I've tested the TimeStamp class only on a Linux machine using
gettimeofday(). If it's utterly broken for ftime(), please scream &
shout and/or fix it. Also the MSVC and Borland project files still need
to be updated for it too.
=20
=20

RE: [Log4cpp-devel] Multiple Appenders at a Category

[Bastiaan B. <Bas...@li...>]

> -----Original Message-----
> From: Tony Cheung [mailto:dra...@as...]
> Sent: Monday, November 26, 2001 9:43 AM
> To: Bastiaan Bakker
> Cc: ton...@as...; log...@li...
> Subject: Re: [Log4cpp-devel] Multiple Appenders at a Category
>=20
>=20
> Hi Bastian,
>=20
> Yes, we think multiple appenders is a big plus, so is a run-time
> configurator and the PatternLayout.
>=20

Both the PatternLayout and a SimpleConfigurator are in CVS and will be
part of 0.2.6. Please try them to  see if they contain any OpenVMS
imcompatibilties.

Regards,

Bastiaan

>=20

Re: [Log4cpp-devel] Multiple Appenders at a Category

[Tony C. <dra...@as...>]

Hi Bastian,

Yes, we think multiple appenders is a big plus, so is a run-time
configurator and the PatternLayout.

Thanks.

Tony

Bastiaan Bakker wrote:

> > -----Original Message-----
> > From: Tony Cheung [mailto:dra...@as...]
> > Sent: Monday, November 26, 2001 7:57 AM
> > To: log...@li...
> > Subject: [Log4cpp-devel] Multiple Appenders at a Category
> >
> >
> > Hi,
> >
> > Is it possible to have mulitple appenders at a single
> > Category? So that
> > one could log to both a file and the console?
> >
> > I am new to log4cpp, but the source tells me that a single Category
> > could only have a single Appender. Is it really the case?
> >
>
> Yes the current version of log4cpp allows a single Category only to have
> 1 Appender at a time. It's a simplification compared to log4j,
> introduced in version 0.0. But it always has been my intention to
> support multiple Appenders eventually. Something for 0.3.0....
>
> Bastiaan
>

RE: [Log4cpp-devel] Multiple Appenders at a Category

[Bastiaan B. <Bas...@li...>]

> -----Original Message-----
> From: Tony Cheung [mailto:dra...@as...]
> Sent: Monday, November 26, 2001 7:57 AM
> To: log...@li...
> Subject: [Log4cpp-devel] Multiple Appenders at a Category
>=20
>=20
> Hi,
>=20
> Is it possible to have mulitple appenders at a single=20
> Category? So that
> one could log to both a file and the console?
>=20
> I am new to log4cpp, but the source tells me that a single Category
> could only have a single Appender. Is it really the case?
>=20

Yes the current version of log4cpp allows a single Category only to have
1 Appender at a time. It's a simplification compared to log4j,
introduced in version 0.0. But it always has been my intention to
support multiple Appenders eventually. Something for 0.3.0....

Bastiaan=20
=20

[Log4cpp-devel] Multiple Appenders at a Category

[Tony C. <dra...@as...>]

Hi,

Is it possible to have mulitple appenders at a single Category? So that
one could log to both a file and the console?

I am new to log4cpp, but the source tells me that a single Category
could only have a single Appender. Is it really the case?

Tony

Re: [Log4cpp-devel] compiling/linking log4cpp with SunW's CC compiler

[Bastiaan B. <bas...@li...>]

James Emery wrote:

>Here's the solution (in case anyone is having the same problem):
>
>./configure --disable-static --prefix=<dir>
>
>in the libtool script, change LD="/usr/ucb/ld" to LD="CC -Kpic"
>
>Regards,
>James
>
Then

export LD="CC -Kpic" && ./configure --disable-static

should do the trick as well? I'll put it in the FAQ.

Regards,

Bastiaan