log4cpp-devel — technical discussions about the development of log4cpp

Re: [Log4cpp-devel] How to enable console output ?

[Konstantin L. <Kon...@ma...>]

Hello, Andy!
You wrote to <log...@li...> on Mon, 19 May 2008 
20:38:37 +0800:


 A> after I call init(), then I write this:

 A> loggg.debug(" Hello, log4cpp!");

    On Windows this code works as expected

#include <log4cpp/Category.hh>
#include <log4cpp/PropertyConfigurator.hh>
#include <iostream>

log4cpp::Category& loggg =
log4cpp::Category::getInstance(std::string("mylog"));

void init()
{

 try
 {
   log4cpp::PropertyConfigurator::configure("log4cpp.properties");
 }
 catch (log4cpp::ConfigureFailure & f)
 {
   std::cerr << "configure problem " << f.what() << std::endl;
 }

}

int main()
{
   init();
   loggg.debug(" Hello, log4cpp!");
   return 0;
}

Print out:

2008-05-21 08:30:38,718 [DEBUG][3476] :  Hello, log4cpp!
2008-05-21 08:30:38,718 [DEBUG][3476] :  Hello, log4cpp!

What log4cpp version, compiler version, OS do you use?

With best regards, Konstantin Litvinenko. 

[Log4cpp-devel] How to enable console output ?

[Andy <hew...@gm...>]

Hi,

This my log4cpp.properties file:

=========================================================
log4cpp.rootCategory=DEBUG, console

log4cpp.appender.console=ConsoleAppender
log4cpp.appender.console.layout=PatternLayout
log4cpp.appender.console.layout.ConversionPattern=%d [%p][%t] : %m%n

log4cpp.category.sample=DEBUG, sample
log4cpp.appender.sample=FileAppender
log4cpp.appender.sample.fileName=sample.log
log4cpp.appender.sample.layout=PatternLayout
log4cpp.appender.sample.layout.ConversionPattern=%d [%p][%t] : %m%n


log4cpp.category.sample.son=DEBUG, son
log4cpp.appender.son=FileAppender
log4cpp.appender.son.fileName=son.log
log4cpp.appender.son.layout=PatternLayout
log4cpp.appender.son.layout.ConversionPattern=%d [%p][%t] : %m%n

log4cpp.category.sample.daughter=DEBUG, daughter
log4cpp.appender.daughter=FileAppender
log4cpp.appender.daughter.fileName=daughter.log
log4cpp.appender.daughter.layout=PatternLayout
log4cpp.appender.daughter.layout.ConversionPattern=%d [%p][%t] : %m%n

log4cpp.category.mylog=DEBUG, mylog
log4cpp.appender.mylog=ConsoleAppender
log4cpp.appender.mylog.layout=PatternLayout
log4cpp.appender.mylog.layout.ConversionPattern=%d [%p][%t] : %m%n
==========================================================


And my code is like this :

------------------------------------------------------------------------------
log4cpp::Category& MscaLog::loggg =
log4cpp::Category::getInstance(std::string("mylog"));

void init()
{	
	
	try
	{
	  log4cpp::PropertyConfigurator::configure("log4cpp.properties");
	}
	catch (log4cpp::ConfigureFailure & f)
	{
	  std::cerr << "configure problem " << f.what() << std::endl;
	}
	
}
-------------------------------------------------------------------------

after I call init(), then I write this:

loggg.debug(" Hello, log4cpp!");

But I got nothing from my console ouput,  is there anything wrong with
my log4cpp.properties  or my way of use log4cpp ?

Thanks for your time.

Best Regards.

[Log4cpp-devel] Registry

[Nuno S. <n_l...@ho...>]

_________________________________________________________________
Instale a Barra de Ferramentas com Desktop Search e ganhe EMOTICONS para o Messenger! É GRÁTIS!
http://www.msn.com.br/emoticonpack

Re: [Log4cpp-devel] MinGW PThreads on Windows

[Konstantin L. <1da...@ma...>]

Hello, Javier!
You wrote to <log...@li...> on Mon, 14 Apr 2008 
16:35:10 +0200:

 JP> I tried to compile log4cpp-1.0 in Windows using MinGW but the configure
 JP> will fail saying that the pthreads where no there, although I put the
 JP> pthread-win32 library and headers in the /lib and /include folders of
 JP> mingw.

    Hm.... I build log4cpp using Boost.Build + gcc-3.4.2(MinGW) just fine. I 
have never try to use MSYS for this. Do you build log4cpp in MSYS 
enviroment?


With best regards, Konstantin Litvinenko. 

[Log4cpp-devel] MinGW PThreads on Windows

[J. P. <xa...@gm...>]

Hi,

I tried to compile log4cpp-1.0 in Windows using MinGW but the configure will
fail saying that the pthreads where no there, although I put the
pthread-win32 library and headers in the /lib and /include folders of mingw.


Then I create a config-mingw32.h file myself and create a project in Eclipse
to compile it there using the -mthreads flag. I had two problems:

1) Priority::ERROR was not recognize.

2) undefine reference to  _imp__pthread_self (although I was using -lpthread
pointing to the pthread-win32 library)

Then I replace in the config-mingw32.h the LOG4CPP_USE_PTHREADS by
LOG4CPP_USE_MSTHREADS and everything worked and compiled fine.

Does anybody know what the problem with the pthreads maybe?

Cheers
Javi

[Log4cpp-devel] log4cpp is now cmake ready

[Thomas W. <wa...@ho...>]

Hi,

Tan Meng YUE has contributed a cmake config file for us.

I have checked it into the cvs and tested it on linux. Seems works nice yet.

Everybody which want to give it a test drive, should checkout the latest 
sources. A short instruction is here:

http://log4cpp.hora-obscura.de/index.php/Building#cmake_-_Cross_pltform_make

Regards and thanks again to Tan Meng YUE

- waffel

[Log4cpp-devel] Log4cpp wiki account

[Swanger, Q. W. (CDC/CCHIS/N. (CTR) <qa...@cd...>]

On the webpage: http://log4cpp.hora-obscura.de/index.php/Welcome_Users
is the following text regarding requesting a wiki account for log4cpp.
My name is Quinn Swanger and I am a C++ developer who would like the use
and also help develop log4cpp.
Will you please create an account for me?
Thank you,
Quinn
qsw...@cd...
qsw...@co...
qsw...@ea...
--------------------------------------------------------------------
		get an wiki account 
		For security reasons (we had spammers which adding some
ugly content to our website), we have disbled the *self account
creation* option. If you want to help us in filling more content, please
send a short mail to our maillinglist (
mailto:log...@li... ) and we create an account
for you. 
		Thanks for your understanding! 
		--Waffel </index.php?title=User:Waffel&action=edit>
13:25, 19 Apr 2005 (CEST)

[Log4cpp-devel] visual C++ 2005 express

[Alejandro D. <Ale...@si...>]

Has someone compiled log4cpp with Visual C++ 2005 express? Trying to
open and compile the Visual 6.0 workspace results in many errors, from
corrupted project to linking errors.
 
Thanks in advance.
A.

[Log4cpp-devel] Vier Doosen umsonst

[Lamont L. <dj...@ev...>]

Online Apotheke - original Qualitaet - 100% wirksam

Spezialangebot: Viiiaaaggra 10 Tab. 100 mg + Ciiiaaaaaallis 10 Tab. x 20 mg 53,82 Euro 

Viiiaaaggra 10 Tab. 26,20 Euro
Viiiaaaggra 30 Tab. 51,97 Euro - Sie sparen: 27,00 Euro
Viiiaaaggra 60 Tab. 95,69 Euro - Sie sparen: 62,00 Euro
Viiiaaaggra 90 Tab. 136,91 Euro - Sie sparen: 100,00 Euro

Ciiiaaaaaallis 10 - 30,00 Euro
Ciiiaaaaaallis 20 - 59,35 Euro - Sie sparen: 2,00 Euro
Ciiiaaaaaallis 30 - 80,30 Euro - Sie sparen: 12,00 Euro

- Kostenlose, arztliche Telefon-Beratung
- Visa verifizierter Onlineshop
- keine versteckte Kosten
- Bequem und diskret online bestellen.
- Diskrete Verpackung und Zahlung
- Kein peinlicher Arztbesuch erforderlich
- Kein langes Warten - Auslieferung innerhalb von 2-3 Tagen

Bestellen Sie jetzt und vergessen Sie Ihre Enttauschungen, anhaltende Versagensaengste und wiederholte peinliche Situationen

Jetzt bestellen - und vier Pillen umsonst erhalten

http://regionpaint.com

[Log4cpp-devel] Thanks and a happy new yer

[Thomas W. <wa...@ho...>]

Hello everybody,

I wish you have a good New Year!

At this point many thanks to all which have contribute to this project!

I hope next year brings any more time for me to investigate into log4cpp
and I hope the project is going on.

So long ...

- waffel

[Log4cpp-devel] DOC does not appear in AM_CONDITIONAL and FTBFS with GCC 4.3

[<fb...@fr...>]

Hi,

this is 2 forwarded bug reports:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=451513

it seems not all necessary m4 defines needed to reproduce the build system
are provided in the tarball:
Makefile.am:1: DOC does not appear in AM_CONDITIONAL

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=455336

For some reason, LOG4CPP_HAVE_SSTREAM is not being set, which it should be,
since GCCs from 3.0 on have <sstream>.

more infos on both bug reports. I joined a build log for #451513.

cheers,

Fathi

Re: [Log4cpp-devel] log4cpp 1.0 needs SONAME change for ABI change

[<fb...@fr...>]

> The LT_VERSION was changed from 4:5:0 to 4:6:0 , but should be 5:5:0.
> Fixed in CVS.

Thanks Konstantin :)

Re: [Log4cpp-devel] log4cpp 1.0 needs SONAME change for ABI change

[Konstantin L. <Kon...@ma...>]

Hello, fb...@fr...!
You wrote to <log...@li...> on Wed, 10 Oct 2007 
15:47:47 +0200:

 f> this is a forwarded bug report:
 f> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=445928

 f> The 1.0 release of log4cpp removed the Category::Stream::operator<<
 f> method that takes Category::Stream::Separator values and indeed the
 f> whole Separator enum in favor of handling ends of lines differently.
 f> This is a change to the public ABI that breaks existing programs and
 f> libraries linked with the log log4cpp and results in run-time load
 f> errors like:

 f> /usr/lib/libsaml.so: undefined reference to
 f> `log4cpp::CategoryStream::operator<<(log4cpp::CategoryStream::Separator)
 f> '

 f> The SONAME of the library needs to be bumped and the package name
 f> changed accordingly.  See also bugs #445778 and #445757.

The LT_VERSION was changed from 4:5:0 to 4:6:0 , but should be 5:5:0.

Fixed in CVS.

With best regards, Konstantin Litvinenko. 

[Log4cpp-devel] log4cpp 1.0 needs SONAME change for ABI change

[<fb...@fr...>]

Hi,

this is a forwarded bug report:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=445928

The 1.0 release of log4cpp removed the Category::Stream::operator<< method
that takes Category::Stream::Separator values and indeed the whole
Separator enum in favor of handling ends of lines differently.  This is a
change to the public ABI that breaks existing programs and libraries
linked with the log log4cpp and results in run-time load errors like:

/usr/lib/libsaml.so: undefined reference to
`log4cpp::CategoryStream::operator<<(log4cpp::CategoryStream::Separator)'

The SONAME of the library needs to be bumped and the package name
changed accordingly.  See also bugs #445778 and #445757.

cheers,

Fathi

Re: [Log4cpp-devel] new account

[Konstantin L. <Kon...@ma...>]

Hello, ren...@bn...!
You wrote to <log...@li...> on Thu, 20 Sep 2007 
10:29:07 +0200:

 rp> I'm try to include log4cpp in my C++ applications.
 rp> Please, could you create an account

 Mmmm.... About what account do you talk?

With best regards, Konstantin Litvinenko. 

[Log4cpp-devel] new account

[<ren...@bn...>]

I'm try to include log4cpp in my C++ applications.

Please, could you create an account

Regards

Rene
This message and any attachments (the "message") is intended solely for the addressees and is confidential. 
If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with 
its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. 
The internet can not guarantee the integrity of this message. 
BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. 
Do not print this message unless it is necessary, consider the environment.
                ---------------------------------------------
Ce message et toutes les pieces jointes (ci-apres le "message") sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce 
message par erreur, merci de le detruire et d'en avertir immediatement l'expediteur. 
Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse.
L'internet ne permettant pas d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales) decline(nt) toute responsabilite au titre de ce message, dans l'hypothese ou il aurait ete modifie.
N'imprimez ce message que si necessaire, pensez a l'environnement.

Re: [Log4cpp-devel] Release 1.0

[Konstantin L. <1da...@ma...>]

Hello, Scott!
You wrote to <log...@li...> on Wed, 5 Sep 2007 
11:59:31 -0400:

??>> If you look on PropertyConfiguratorImpl.cpp you will see that
??>> PropertyConfiguratorImpl knows all about appenders/layouts/etc that
??>> exists in the library. But if I write my own appender or layout it
??>> can't be configured with help of PropertyConfigurator because it
??>> doesn't know anything about it. If PropertyConfigurator will be
??>> rewrited using Factory stuffs it will be generic and can be used for
??>> configuring my appender/layout.

SC> So it hasn't been reimplemented yet to support this?

    No. I think I can do such rewrite. It's pretty easy. I wrote xml 
configurator based on factories for my company. It's much more simple than 
PropertyConfigurator.

With best regards, Konstantin Litvinenko. 

Re: [Log4cpp-devel] Release 1.0

[Scott C. <can...@os...>]

> Purpose of this machinery is to provide a way to write different
> configurators that independed of knowledge what appenders/layout/etc
> exists.

I understand, it's for dynamically creating the objects so the configuration
doesn't have to know the classes at compile time.

> If you look on PropertyConfiguratorImpl.cpp you will see that
> PropertyConfiguratorImpl knows all about appenders/layouts/etc that exists
> in the library. But if I write my own appender or layout it can't be
> configured with help of PropertyConfigurator because it doesn't know
> anything about it. If PropertyConfigurator will be rewrited using Factory
> stuffs it will be generic and can be used for configuring my
> appender/layout.

So it hasn't been reimplemented yet to support this?

-- Scott

Re: [Log4cpp-devel] Release 1.0

[Konstantin L. <1da...@ma...>]

Hello, Scott!
You wrote to "'Konstantin Litvinenko'" <1da...@ma...>;
<log...@li...> on Wed, 5 Sep 2007 11:36:14 -0400:

??>> Fixed. It was vary hard because msvc6 is not true C++ compiler. No
??>> true template member function is really pain. Linking error was really
??>> nasty. Its unfixable in 'a right way'. I have to instantiate manually
??>> CategoryStream::operator << for basic types and std::string and
std::wstring. Please, check it. I am
??>> not sure Factory stuff workable under msvc6, but as I understand you
??>> don't need it anyway.

SC> No, I don't use it. Is there a brief description of what it does?

    Nope. My english is too bad to make such usefull description :((.
Purpose of this machinery is to provide a way to write different
configurators that independed of knowledge what appenders/layout/etc exists.
If you look on PropertyConfiguratorImpl.cpp you will see that
PropertyConfiguratorImpl knows all about appenders/layouts/etc that exists
in the library. But if I write my own appender or layout it can't be
configured with help of PropertyConfigurator because it doesn't know
anything about it. If PropertyConfigurator will be rewrited using Factory
stuffs it will be generic and can be used for configuring my
appender/layout.

SC> I'll pull the tree again and try it out.

    I tested it on msvc6 + sp5.

With best regards, Konstantin Litvinenko. 

Re: [Log4cpp-devel] Release 1.0

[Scott C. <can...@os...>]

> Fixed. It was vary hard because msvc6 is not true C++ compiler. No true
> template member function is really pain. Linking error was really nasty.
> Its unfixable in 'a right way'. I have to instantiate manually
> CategoryStream::operator << for basic types and std::string and
> std::wstring. Please, check it. I am not sure Factory stuff workable under
> msvc6, but as I understand you don't need it anyway.

No, I don't use it. Is there a brief description of what it does?

I'll pull the tree again and try it out.

-- Scott

Re: [Log4cpp-devel] Release 1.0

[Konstantin L. <1da...@ma...>]

Hello, Scott!
You wrote to <log...@li...> on Mon, 3 Sep 2007 
18:30:25 -0400:

 SC> Unfortunately the Windows errors aren't simple. I think the Factory
 SC> stuff is using function templates in some way that doesn't work on the
 SC> older Microsoft compiler, and there's some kind of linker error with
 SC> the newer compiler.

 SC> That one's just going to take some work, but the template error is
 SC> probably not fixable without changing a lot of code I haven't seen (the
 SC> Factory API post-dates anything I've seen in the code, and I don't know
 SC> what it does yet).

 SC> I need VC6 compatibility for the foreseeable future, so I may need to
 SC> stay with my fork of the code if there isn't a volunteer to work on
 SC> that, or some simple way to just compile out the factory API. Is there
 SC> a description somewhere of what that does? Is it optional, or is it
 SC> used internally now?

    Fixed. It was vary hard because msvc6 is not true C++ compiler. No true 
template member function is really pain. Linking error was really nasty. Its 
unfixable in 'a right way'. I have to instantiate manually 
CategoryStream::operator << for basic types and std::string and 
std::wstring. Please, check it. I am not sure Factory stuff workable under 
msvc6, but as I understand you don't need it anyway.

With best regards, Konstantin Litvinenko. 

Re: [Log4cpp-devel] Release 1.0

[Konstantin L. <1da...@ma...>]

Hello, Scott!
You wrote to <log...@li...> on Tue, 4 Sep 2007 
11:04:45 -0400:

??>>     Scott, it is my code and I will fix it very soon, I hope.

SC> Sounds like you have access to VC6 from your response,

    Yes :)

SC> but if not I can feed you the error messages in a bug report.

     There is no need to do this. I am allmost fix this.

 With best regards, Konstantin Litvinenko. 

Re: [Log4cpp-devel] Release 1.0

[Scott C. <can...@os...>]

>     Scott, it is my code and I will fix it very soon, I hope.

Sounds like you have access to VC6 from your response, but if not I can feed
you the error messages in a bug report.

-- Scott

Re: [Log4cpp-devel] Release 1.0

[Konstantin L. <1da...@ma...>]

Hello, Scott!
You wrote to <log...@li...> on Mon, 3 Sep 2007 
18:30:25 -0400:

SC> Unfortunately the Windows errors aren't simple. I think the Factory
SC> stuff is using function templates in some way that doesn't work on the
SC> older Microsoft compiler, and there's some kind of linker error with
SC> the newer compiler.

SC> That one's just going to take some work, but the template error is
SC> probably not fixable without changing a lot of code I haven't seen (the
SC> Factory API post-dates anything I've seen in the code, and I don't know
SC> what it does yet).

SC> I need VC6 compatibility for the foreseeable future, so I may need to
SC> stay with my fork of the code if there isn't a volunteer to work on
SC> that, or some simple way to just compile out the factory API. Is there
SC> a description somewhere of what that does? Is it optional, or is it
SC> used internally now?

    Scott, it is my code and I will fix it very soon, I hope.

With best regards, Konstantin Litvinenko. 

Re: [Log4cpp-devel] Release 1.0

[Scott C. <can...@os...>]

Unfortunately the Windows errors aren't simple. I think the Factory stuff is
using function templates in some way that doesn't work on the older
Microsoft compiler, and there's some kind of linker error with the newer
compiler.

That one's just going to take some work, but the template error is probably
not fixable without changing a lot of code I haven't seen (the Factory API
post-dates anything I've seen in the code, and I don't know what it does
yet).

I need VC6 compatibility for the foreseeable future, so I may need to stay
with my fork of the code if there isn't a volunteer to work on that, or some
simple way to just compile out the factory API. Is there a description
somewhere of what that does? Is it optional, or is it used internally now?

-- Scott