You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(10) |
Dec
(3) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(17) |
Feb
(11) |
Mar
(2) |
Apr
(6) |
May
(17) |
Jun
(17) |
Jul
(4) |
Aug
(19) |
Sep
(21) |
Oct
(17) |
Nov
(6) |
Dec
(6) |
2003 |
Jan
(6) |
Feb
(6) |
Mar
(14) |
Apr
(16) |
May
(9) |
Jun
|
Jul
(4) |
Aug
(4) |
Sep
(1) |
Oct
(3) |
Nov
(1) |
Dec
(1) |
2004 |
Jan
(4) |
Feb
(3) |
Mar
|
Apr
(6) |
May
|
Jun
|
Jul
(2) |
Aug
(1) |
Sep
|
Oct
|
Nov
(3) |
Dec
|
2005 |
Jan
(1) |
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
(7) |
Aug
(1) |
Sep
(8) |
Oct
(6) |
Nov
(4) |
Dec
(6) |
2006 |
Jan
(1) |
Feb
(7) |
Mar
|
Apr
|
May
(3) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
(4) |
Oct
|
Nov
(6) |
Dec
(1) |
2007 |
Jan
|
Feb
|
Mar
(7) |
Apr
(3) |
May
|
Jun
(4) |
Jul
(5) |
Aug
(35) |
Sep
(13) |
Oct
(3) |
Nov
|
Dec
(2) |
2008 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
(4) |
May
(5) |
Jun
|
Jul
|
Aug
(2) |
Sep
(4) |
Oct
|
Nov
(2) |
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(12) |
Nov
(1) |
Dec
|
2010 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2011 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(2) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
|
Feb
(3) |
Mar
|
Apr
(6) |
May
|
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
(5) |
Nov
|
Dec
(2) |
2013 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
(3) |
Feb
(3) |
Mar
(6) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
From: Bastiaan B. <Bas...@li...> - 2002-12-19 11:14:00
|
Hi Betty, The Makefiles in log4cpp are automatically generated from the Makefile.am files by automake/autoconf. Editting a Makefile.am will only work if you have the automake and autoconf packages installed. Also the target 'testCategory', etc. will not be build if you type just 'make', since the are not part of the default make target. (you need to do 'make check'.) So to get started it's probably easier to try the hand written one-liner. You almost got it right, except for two things: 1) Since the source is C++ use 'g++' instead of 'gcc' or else the compiler won't link the necessary standard C++ libraries 2) It does link the log4cpp library. I assume you've build and installed log4cpp using './configure --prefix=<installdir> ; make ; make install' Then you can ask the tool log4cpp-config which parameters you need for linking log4cpp with 'log4cpp-config --libs'. It will return something like '-L<installdir> -llog4cpp', maybe followed by '-lsocket -lnsl' or something similar. The same trick also works for the compile flags. In short, try: g++ `log4cpp-config --cflags` `log4cpp-config --libs` -o testLog testLog.cpp Good luck, Bastiaan Bakker LifeLine Networks bv On Fri, 2002-12-13 at 11:05, Betty Goh wrote: > Dear all, > > This is really basic level question, but I couldn't find the answer anywhere in the list. So hopefully someone's coming to my rescue as I'm really clueless as to how to compile. :) > > I've written a simple program (basically copied from a technical article from the Solaris Developer Connection). But I have no idea as to how to compile it. > > I tried adding it to the tests directory and modified the Makefile to include my source code, it doesn't work. The Makefile simply ignores my source code. > > Then I tried doing a one-liner like this: > gcc -DHAVE_CONFIG_H -I. -I/home/bgoh2/log4cpp-0.3.4b/tests -I/home/bgoh2/log4cpp-0.3.4b/include > -I/home/bgoh2/log4cpp-0.3.4b/src testLog.cpp > > I get a lot of undefined references to the .hh files, which is strange because the files are all there. > > I would be really grateful if someone can point me in the right direction.. :) > > Many thanks, > Betty > -- > Get your free email from www.doramail.com with 30 Megs of disk space in webhosting and e-mail storage! > > > > > > Powered by Outblaze > > > ------------------------------------------------------- > This sf.net email is sponsored by: > With Great Power, Comes Great Responsibility > Learn to use your power at OSDN's High Performance Computing Channel > http://hpc.devchannel.org/ > _______________________________________________ > Log4cpp-devel mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/log4cpp-devel |
From: Bastiaan B. <Bas...@li...> - 2002-12-19 10:52:22
|
Hi Greg, You seem to have a problem with loading the log4cpp shared library. Whether that's due to inherent AIX OS problems, your particular system setup, libtool or compiler shortcomings or even faulty log4cpp code, I don't know. But you could try to compile log4cpp as a static lib to see if that resolves the problem: ./configure --disable-shared --enable-static Also searching for documentation on libtool support for AIX may help: libtools jobs is to shield us from the gory details of library loading and linking on multiple platforms, your problem may indicate that libtool needs some tweaking on AIX. Good luck, Bastiaan Bakker LifeLine Networks bv On Thu, 2002-12-19 at 03:52, Beresnev, Greg wrote: > > hi there guys, > > I've tried compiling log4cpp on my AIX machine, and after > ./configure > make > make check > > got the following: > > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > make check-TESTS > exec(): 0509-036 Cannot load program testCategory because of the following errors: > 0509-150 Dependent module liblog4cpp.a(liblog4cpp.so.1) could not be loaded. > 0509-022 Cannot load module liblog4cpp.a(liblog4cpp.so.1). > 0509-026 System error: A file or directory in the path name does not exist. > FAIL: testCategory > exec(): 0509-036 Cannot load program testFixedContextCategory because of the following errors: > 0509-150 Dependent module liblog4cpp.a(liblog4cpp.so.1) could not be loaded. > 0509-022 Cannot load module liblog4cpp.a(liblog4cpp.so.1). > 0509-026 System error: A file or directory in the path name does not exist. > FAIL: testFixedContextCategory > exec(): 0509-036 Cannot load program testNDC because of the following errors: > 0509-150 Dependent module liblog4cpp.a(liblog4cpp.so.1) could not be loaded. > 0509-022 Cannot load module liblog4cpp.a(liblog4cpp.so.1). > 0509-026 System error: A file or directory in the path name does not exist. > FAIL: testNDC > exec(): 0509-036 Cannot load program testPattern because of the following errors: > 0509-150 Dependent module liblog4cpp.a(liblog4cpp.so.1) could not be loaded. > 0509-022 Cannot load module liblog4cpp.a(liblog4cpp.so.1). > 0509-026 System error: A file or directory in the path name does not exist. > FAIL: testPattern > exec(): 0509-036 Cannot load program testErrorCollision because of the following errors: > 0509-150 Dependent module liblog4cpp.a(liblog4cpp.so.1) could not be loaded. > 0509-022 Cannot load module liblog4cpp.a(liblog4cpp.so.1). > 0509-026 System error: A file or directory in the path name does not exist. > FAIL: testErrorCollision > exec(): 0509-036 Cannot load program testConfig because of the following errors: > 0509-150 Dependent module liblog4cpp.a(liblog4cpp.so.1) could not be loaded. > 0509-022 Cannot load module liblog4cpp.a(liblog4cpp.so.1). > 0509-026 System error: A file or directory in the path name does not exist. > FAIL: testConfig > exec(): 0509-036 Cannot load program testPriority because of the following errors: > 0509-150 Dependent module liblog4cpp.a(liblog4cpp.so.1) could not be loaded. > 0509-022 Cannot load module liblog4cpp.a(liblog4cpp.so.1). > 0509-026 System error: A file or directory in the path name does not exist. > FAIL: testPriority > exec(): 0509-036 Cannot load program testFilter because of the following errors: > 0509-150 Dependent module liblog4cpp.a(liblog4cpp.so.1) could not be loaded. > 0509-022 Cannot load module liblog4cpp.a(liblog4cpp.so.1). > 0509-026 System error: A file or directory in the path name does not exist. > FAIL: testFilter > =================== > 8 of 8 tests failed > =================== > make: 1254-004 The error code from the last command is 1. > > > Stop. > make: 1254-004 The error code from the last command is 2. > > > Stop. > make: 1254-004 The error code from the last command is 1. > > > Stop. > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Above error can be fixed by adding the path to liblog4cpp.a to the LIBPATH variable > but then the result of make check is: > > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > make check-TESTS > /bin/sh: 3184 Segmentation fault(coredump) > FAIL: testCategory > /bin/sh: 3190 Segmentation fault(coredump) > FAIL: testFixedContextCategory > /bin/sh: 3196 Segmentation fault(coredump) > FAIL: testNDC > /bin/sh: 3202 Segmentation fault(coredump) > FAIL: testPattern > /bin/sh: 3208 Segmentation fault(coredump) > FAIL: testErrorCollision > /bin/sh: 3214 Segmentation fault(coredump) > FAIL: testConfig > /bin/sh: 3220 Segmentation fault(coredump) > FAIL: testPriority > /bin/sh: 3226 Segmentation fault(coredump) > FAIL: testFilter > =================== > 8 of 8 tests failed > =================== > make: 1254-004 The error code from the last command is 1. > > > Stop. > make: 1254-004 The error code from the last command is 2. > > > Stop. > make: 1254-004 The error code from the last command is 1. > > > Stop. > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Was wondering what you thought of this, and whether it is my system configuration to blame.. > > regards, > > Greg |
From: Garhoefer A. <and...@si...> - 2002-12-19 10:24:57
|
hi to all! I would like to use the log4j SocketServer for C++ apps (using log4cpp). As far as I can see, the SocketAppender sends (serialized) objects over the net which are java-specific. So using log4cpp from a C++ application means that I have to write an appender which is able to creates serialized objects. Has anybody done that already ? regards andreas garhoefer |
From: Beresnev, G. <GRE...@ca...> - 2002-12-19 02:51:48
|
hi there guys, I've tried compiling log4cpp on my AIX machine, and after ./configure make make check got the following: -------------------------------------------------------------------------= -------------------------------------------------------------------------= ------------------------ make check-TESTS exec(): 0509-036 Cannot load program testCategory because of the = following errors: 0509-150 Dependent module liblog4cpp.a(liblog4cpp.so.1) could = not be loaded. 0509-022 Cannot load module liblog4cpp.a(liblog4cpp.so.1). 0509-026 System error: A file or directory in the path name does = not exist. FAIL: testCategory exec(): 0509-036 Cannot load program testFixedContextCategory because of = the following errors: 0509-150 Dependent module liblog4cpp.a(liblog4cpp.so.1) could = not be loaded. 0509-022 Cannot load module liblog4cpp.a(liblog4cpp.so.1). 0509-026 System error: A file or directory in the path name does = not exist. FAIL: testFixedContextCategory exec(): 0509-036 Cannot load program testNDC because of the following = errors: 0509-150 Dependent module liblog4cpp.a(liblog4cpp.so.1) could = not be loaded. 0509-022 Cannot load module liblog4cpp.a(liblog4cpp.so.1). 0509-026 System error: A file or directory in the path name does = not exist. FAIL: testNDC exec(): 0509-036 Cannot load program testPattern because of the = following errors: 0509-150 Dependent module liblog4cpp.a(liblog4cpp.so.1) could = not be loaded. 0509-022 Cannot load module liblog4cpp.a(liblog4cpp.so.1). 0509-026 System error: A file or directory in the path name does = not exist. FAIL: testPattern exec(): 0509-036 Cannot load program testErrorCollision because of the = following errors: 0509-150 Dependent module liblog4cpp.a(liblog4cpp.so.1) could = not be loaded. 0509-022 Cannot load module liblog4cpp.a(liblog4cpp.so.1). 0509-026 System error: A file or directory in the path name does = not exist. FAIL: testErrorCollision exec(): 0509-036 Cannot load program testConfig because of the following = errors: 0509-150 Dependent module liblog4cpp.a(liblog4cpp.so.1) could = not be loaded. 0509-022 Cannot load module liblog4cpp.a(liblog4cpp.so.1). 0509-026 System error: A file or directory in the path name does = not exist. FAIL: testConfig exec(): 0509-036 Cannot load program testPriority because of the = following errors: 0509-150 Dependent module liblog4cpp.a(liblog4cpp.so.1) could = not be loaded. 0509-022 Cannot load module liblog4cpp.a(liblog4cpp.so.1). 0509-026 System error: A file or directory in the path name does = not exist. FAIL: testPriority exec(): 0509-036 Cannot load program testFilter because of the following = errors: 0509-150 Dependent module liblog4cpp.a(liblog4cpp.so.1) could = not be loaded. 0509-022 Cannot load module liblog4cpp.a(liblog4cpp.so.1). 0509-026 System error: A file or directory in the path name does = not exist. FAIL: testFilter =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 8 of 8 tests failed =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D make: 1254-004 The error code from the last command is 1. Stop. make: 1254-004 The error code from the last command is 2. Stop. make: 1254-004 The error code from the last command is 1. Stop. -------------------------------------------------------------------------= -------------------------------------------------------------------------= ------------------------ Above error can be fixed by adding the path to liblog4cpp.a to the = LIBPATH variable but then the result of make check is: -------------------------------------------------------------------------= -------------------------------------------------------------------------= ------------------------ make check-TESTS /bin/sh: 3184 Segmentation fault(coredump) FAIL: testCategory /bin/sh: 3190 Segmentation fault(coredump) FAIL: testFixedContextCategory /bin/sh: 3196 Segmentation fault(coredump) FAIL: testNDC /bin/sh: 3202 Segmentation fault(coredump) FAIL: testPattern /bin/sh: 3208 Segmentation fault(coredump) FAIL: testErrorCollision /bin/sh: 3214 Segmentation fault(coredump) FAIL: testConfig /bin/sh: 3220 Segmentation fault(coredump) FAIL: testPriority /bin/sh: 3226 Segmentation fault(coredump) FAIL: testFilter =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 8 of 8 tests failed =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D make: 1254-004 The error code from the last command is 1. Stop. make: 1254-004 The error code from the last command is 2. Stop. make: 1254-004 The error code from the last command is 1. Stop. -------------------------------------------------------------------------= -------------------------------------------------------------------------= ------------------------ Was wondering what you thought of this, and whether it is my system = configuration to blame.. regards, Greg |
From: Betty G. <bet...@do...> - 2002-12-13 10:05:59
|
Dear all, This is really basic level question, but I couldn't find the answer anywhere in the list. So hopefully someone's coming to my rescue as I'm really clueless as to how to compile. :) I've written a simple program (basically copied from a technical article from the Solaris Developer Connection). But I have no idea as to how to compile it. I tried adding it to the tests directory and modified the Makefile to include my source code, it doesn't work. The Makefile simply ignores my source code. Then I tried doing a one-liner like this: gcc -DHAVE_CONFIG_H -I. -I/home/bgoh2/log4cpp-0.3.4b/tests -I/home/bgoh2/log4cpp-0.3.4b/include -I/home/bgoh2/log4cpp-0.3.4b/src testLog.cpp I get a lot of undefined references to the .hh files, which is strange because the files are all there. I would be really grateful if someone can point me in the right direction.. :) Many thanks, Betty -- Get your free email from www.doramail.com with 30 Megs of disk space in webhosting and e-mail storage! Powered by Outblaze |
From: Aaron I. <ai...@ya...> - 2002-11-19 21:29:36
|
Hi all, I have an ancestor Category, A, that has certain Appenders that I'd like its heir, B, to inherit. This is easily done by letting B's additivity default to true. However, what if I don't want one of A's appenders, X, to be inherited? I could set B's additivity to false and then add the remaining appenders to B, but I'd have to do that for all such heirs. Since that would obviously be a maintenance headache, I'd like to find a better solution. I'm considering creating a Filter, PrivateFilter, that effectively allows me to mark an appender as private, i.e. heirs will not inherit the appender even if they are additive. I'm also considering not attaching X to A, but instead creating a child A' that attaches X. I'd then log using A' in place of A. Does anyone have an alternative solution or comments to the above? Thanks in advance. -Aaron __________________________________________________ Do you Yahoo!? Yahoo! Web Hosting - Let the expert host your site http://webhosting.yahoo.com |
From: Gary G. <gr...@at...> - 2002-11-12 17:38:03
|
Across the ether fly the words of Colin Law: > ... > log4cpp::Category A::main_cat = log4cpp::Category::getRoot() ; getRoot() returns a reference, so main_cat needs to be declared and defined as a reference: log4cpp::Category& A::main_cat = log4cpp::Category::getRoot() ; The error is caused because your definition without the reference is attempting to call the copy constructor, which is private. gary |
From: Colin L. <c....@el...> - 2002-11-12 17:20:48
|
Hi, With a recent upgrade to log4cpp 0.3.4b, and a new gentoo linux system using g++3.2, i can no longer get a simple example to compile. The error is; /usr/local/log4cpp-0.3.3/include/log4cpp/Category.hh: In static member function `void __static_initialization_and_destruction_0(int, int)': /usr/local/log4cpp-0.3.3/include/log4cpp/Category.hh:624: ` log4cpp::Category::Category(const log4cpp::Category&)' is private test.cc:15: within this context This compiles fine with log4cpp 0.2.5 under debian using g++2.95.4. I have tried a trivial example moving everything into main as in testmain.cpp from the examples directory, which compiles and runs fine. Can someone point out what im doing wrong, or perhaps how i should be setting up so each class can log effeciently. #include "log4cpp/Category.hh" class A { public: A() ; ~A() ; void testMethod() ; static log4cpp::Category main_cat ; }; log4cpp::Category A::main_cat = log4cpp::Category::getRoot() ; A::A() {} void A::testMethod() { main_cat.log(log4cpp::Priority::ERROR, "This is a test!"); } A::~A() {} int main(int argc, char* argv[]) { A a ; a.testMethod() ; return (0); } Thanks for any help, ~Colin. |
From: Simon J. J. <sj...@er...> - 2002-11-09 13:35:47
|
I just started to use log4cpp a couple of months ago (very nice) for a project running under linux and cygwin using log4cpp and boost. (log4cpp works "out of the box" for cygwin with no modifications and changes. The only problem I have encountered is that the PropertyConfigurator doesn't like a configuration file with ^Ms in it and generates fairly bizarre parsing errors.) In the threads include directory there is the BoostThreads.hh header file which seems to provide an interface to the boost threading library. However, there currently doesn't seem to be a way to configure and use this option (without directly hacking the configuration files). Please could you let me know the current status / future plans for boost::threads are? Yours sincerely, Simon Julier |
From: Bastiaan B. <Bas...@li...> - 2002-11-07 16:51:33
|
On Tue, 2002-11-05 at 15:21, Heinrich G=F6tzger wrote:=20 > Salve, >=20 > from log4j I learned that there is a log4cpp available. I'd like to use i= t > in a testserver written in C++ (running under Linux Kernel 2.x) to get ri= d > of all these cout stuff. (That's what loggin is for actually ;-) > I'm used to work with log4j and I like it. >=20 If you're familiar with log4j, getting started with log4cpp shouldn't be di= fficult. Initialize the logging with PropertyConfigurator::configure(), grab a log c= ategory with Category::getInstance("some.log.category") and start logging with warn(), i= nfo(), etc. One thing to note is that log4cpp still uses the old log4j class names, lik= e Category and Priority, instead of the new JDK1.4 compatible names Logger and Level.=20 Of course log4cpp is nowhere near a complete C++ log4j implementation,=20 it doesn't have database appenders, an XML configurator, multiple logger re= positories, etc. But, since you're switching from simple 'std::cout' style logging, I expect= that the current feature set is rich enough. =20 > So here's my question: Can I just start using it as I'm used to work with > log4j or are there some critical issues for not taking it in semi > productional code? There are no critical issues I'm aware of. At LifeLine we use the latest lo= g4cpp release (0.3.4b) ourselves, without problems.=20 Nevertheless if you encounter crashes, leaks, dead-locks, etc. caused by lo= g4cpp=20 please report! We need to have them fixed, for both your and our sake. >=20 > Which release would I use or should I go with cvs? Try 0.3.4b. Go with CVS only if you need features not present in the latest release (none at the moment) or want to help with log4cpp development. =20 >=20 > If this is not the right place to ask, point me to the right address > please. Well, actually this list is about development of log4cpp, but since I prefe= r this mailing list over those inconvienient web forums, I don't mind. Cheers, Bastiaan >=20 > Thanks. >=20 > cheers >=20 > Heinrich >=20 >=20 >=20 > ------------------------------------------------------- > This sf.net email is sponsored by: See the NEW Palm=20 > Tungsten T handheld. Power & Color in a compact size! > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en > _______________________________________________ > Log4cpp-devel mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/log4cpp-devel |
From: <Hei...@ex...> - 2002-11-05 14:21:42
|
Salve, from log4j I learned that there is a log4cpp available. I'd like to use it in a testserver written in C++ (running under Linux Kernel 2.x) to get rid of all these cout stuff. (That's what loggin is for actually ;-) I'm used to work with log4j and I like it. So here's my question: Can I just start using it as I'm used to work with log4j or are there some critical issues for not taking it in semi productional code? Which release would I use or should I go with cvs? If this is not the right place to ask, point me to the right address please. Thanks. cheers Heinrich |
From: Bastiaan B. <bas...@li...> - 2002-10-29 21:48:43
|
Hi, I just put release 0.3.4b on SourceForge. Builds for both MSVC6 and MSVC7 should finally be OK now. For other platforms there are no differences compared to 0.3.4. Cheers, Bastiaan |
From: Bastiaan B. <bas...@li...> - 2002-10-28 22:15:29
|
Hi Mohamad, Thanks for the reports: A) I've committed your suggestions. I don't know whether old code was standard C++ compliant, but having both trim() methods return the same type is cleaner anyway. B) I don't know. If MSVC gives warning, that should signify something, right? :-) Since it doesn't break the build, I'll let it be, unless you're really sure that the #pragma is OK. C) That's a fix, not a workaround! I noticed it just before receiving your mail, so it has already been commited. Thanks, Bastiaan PS. To make the MSVC6 users happy I'll release 0.3.4 immediately. On Mon, 2002-10-28 at 22:44, Daniar, Mohamad wrote: > A. > > c:\CVS\0.3.3\log4cpp\src\StringUtil.hh(78) : error > C2785: 'unsigned int log4cpp::StringUtil::split(T > &,const std::string &,char,unsigned int)' and 'void > log4cpp::StringUtil::split(std::vector<_Ty,_Ax> > &,const std::string &,char,unsigned int)' have > different return types > with > [ > _Ty=std::string, > _Ax=std::allocator<std::string> > ] > c:\CVS\0.3.3\log4cpp\src\StringUtil.hh(62) : see > declaration of 'log4cpp::StringUtil::split' > c:\CVS\0.3.3\log4cpp\src\StringUtil.hh(49) : see > declaration of 'log4cpp::StringUtil::split' > c:\CVS\0.3.3\log4cpp\src\StringUtil.cpp(45) : warning > C4018: '<' : signed/unsigned mismatch > > [mdaniar] Possible workaround : Should both of them > return unsigned int ? > > > B. > > c:\CVS\0.3.3\log4cpp\include\log4cpp\Configurator.hh(21) > : warning C4275: non dll-interface class > 'std::runtime_error' used as base for dll-interface > class 'log4cpp::ConfigureFailure' > c:\Program Files\Microsoft Visual Studio > .NET\Vc7\include\stdexcept(137) : see declaration of > 'std::runtime_error' > c:\CVS\0.3.3\log4cpp\include\log4cpp\Configurator.hh(21) > : see declaration of 'log4cpp::ConfigureFailure' > > [mdaniar] Possible workaround : #pragma > warning(disable : 4275) > > C. > > testPattern.cpp > c:\CVS\0.3.3\log4cpp\tests\testPattern.cpp(16) : error > C2039: 'cerr' : is not a member of 'std' > c:\CVS\0.3.3\log4cpp\tests\testPattern.cpp(16) : error > C2065: 'cerr' : undeclared identifier > c:\CVS\0.3.3\log4cpp\tests\testPattern.cpp(16) : error > C2296: '<<' : illegal, left operand has type > ''unknown-type'' > c:\CVS\0.3.3\log4cpp\tests\testPattern.cpp(16) : error > C2297: '<<' : illegal, right operand has type 'char > [20]' > > [mdaniar] Possible workaround : include #iostream in > testPattern.cpp > > > thanks, > > Mohamad > > --- Bastiaan Bakker <bas...@li...> > wrote: > > Hi Mohamad, > > > > Thanks for the quick report. > > * The compile errors in PatternLayout.cpp are caused > > by initializing > > static constant strings at declaration point, which > > GCC accepts, but is > > not standards compliant C++. I think I should switch > > to GCC 3.2 as > > primary development compiler, as it gives a proper > > warning for it when > > compiling with '-pedantic'. > > I've moved the definition of these strings outside > > the class declaration > > to fix the comile problem. > > > > * PortabilityImpl.cpp was not committed to CVS yet, > > but it is not part > > of 0.3.3: I added it after the 0.3.3 release. I > > guess you checked out > > CVS HEAD, rather than REL_0_3_3. I've added it now. > > > > * BasicConfigurator was misssing from both the MSVC > > and BCB5 project > > files. I've added it now. In the long term I like to > > have a mechanism to > > update them automatically if a file is added to the > > automake files. > > Having to update 6(!) project files for the addition > > of one source file > > is no fun. Suggestions or code to alleviate this > > problem are very > > welcome.... > > > > * MSVC7 compile problems: please mail them.... > > > > Thanks, > > > > Bastiaan > > > > > > On Sun, 2002-10-27 at 13:22, Daniar, Mohamad wrote: > > > Hi : > > > Downloaded 0.3.3 through CVS, > > > > > > Got this error for log4cpp.lib, > > > d:\log4cpp\src\patternlayout.cpp(127) : error > > C2258: > > > illegal pure syntax, must be '= 0' > > > d:\log4cpp\src\patternlayout.cpp(127) : error > > C2252: > > > 'FORMAT_ISO8601' : pure specifier can only be > > > specified for functions > > > d:\log4cpp\src\patternlayout.cpp(128) : error > > C2258: > > > illegal pure syntax, must be '= 0' > > > d:\log4cpp\src\patternlayout.cpp(128) : error > > C2252: > > > 'FORMAT_ABSOLUTE' : pure specifier can only be > > > specified for functions > > > d:\log4cpp\src\patternlayout.cpp(129) : error > > C2258: > > > illegal pure syntax, must be '= 0' > > > d:\log4cpp\src\patternlayout.cpp(129) : error > > C2252: > > > 'FORMAT_DATE' : pure specifier can only be > > specified > > > for functions > > > PortabilityImpl.cpp > > > fatal error C1083: Cannot open source file: > > > 'D:\log4cpp\src\PortabilityImpl.cpp': No such file > > or > > > directory > > > > > > Had to add BasicConfigurator.cpp / .hh in > > log4cpp.dsp > > > > > > btw: > > > Tried to compile it using Visual C++ 7, > > > Seems like MS fix the std:: problem (no need to > > > workaround) > > > but there's some new warnings and error, will mail > > > them if interested. > > > > > > > > > thanks, > > > > > > > > > Mohamad > > > > > > --- Bastiaan Bakker <bas...@li...> > > > wrote: > > > > Hi, > > > > > > > > I've put 0.3.3 on SourceForge. It's a relatively > > > > small update to 0.3.2, > > > > the two most important changes are: > > > > * build fixes for MSVC. 0.3.3 introduces > > > > PortabilityImpl.hh, an internal > > > > header file for portibality stuff that should > > not be > > > > part of the API. It > > > > contains aliases in namespace 'std' for the > > > > functions in <cstlib> and > > > > <cstring> we use but MSVC mistakenly puts in the > > > > global namespace. > > > > * a new PatternLayout implementation. It > > preparses > > > > the conversionpattern > > > > into a vector of PatternComponents. This should > > make > > > > it speedier and > > > > more flexible. PatternLayout now also support > > > > formatting specifiers like > > > > '%-5.5p'. > > > > > > > > Please report any bugs/problems through the > > normal > > > > channels (bug tracker > > > > or mailing list). > > > > > > > > Cheers, > > > > > > > > Bastiaan > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > This SF.net email is sponsored by: ApacheCon, > > > > November 18-21 in > > > > Las Vegas (supported by COMDEX), the only Apache > > > > event to be > > > > fully supported by the ASF. > > http://www.apachecon.com > > > > _______________________________________________ > > > > Log4cpp-devel mailing list > > > > Log...@li... > > > > > > > > > > https://lists.sourceforge.net/lists/listinfo/log4cpp-devel > > > > > > > > > __________________________________________________ > > > Do you Yahoo!? > > > Y! Web Hosting - Let the expert host your web site > > > http://webhosting.yahoo.com/ > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.net email is sponsored by: ApacheCon, > > November 18-21 in > > > Las Vegas (supported by COMDEX), the only Apache > > event to be > > > fully supported by the ASF. > > http://www.apachecon.com > > > _______________________________________________ > > > Log4cpp-devel mailing list > > > Log...@li... > > > > > > https://lists.sourceforge.net/lists/listinfo/log4cpp-devel > > > > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: ApacheCon, > > November 18-21 in > > Las Vegas (supported by COMDEX), the only Apache > > event to be > > fully supported by the ASF. http://www.apachecon.com > > _______________________________________________ > > Log4cpp-devel mailing list > > Log...@li... > > > https://lists.sourceforge.net/lists/listinfo/log4cpp-devel > > > __________________________________________________ > Do you Yahoo!? > Y! Web Hosting - Let the expert host your web site > http://webhosting.yahoo.com/ |
From: Daniar, M. <da...@ya...> - 2002-10-28 21:44:47
|
A. c:\CVS\0.3.3\log4cpp\src\StringUtil.hh(78) : error C2785: 'unsigned int log4cpp::StringUtil::split(T &,const std::string &,char,unsigned int)' and 'void log4cpp::StringUtil::split(std::vector<_Ty,_Ax> &,const std::string &,char,unsigned int)' have different return types with [ _Ty=std::string, _Ax=std::allocator<std::string> ] c:\CVS\0.3.3\log4cpp\src\StringUtil.hh(62) : see declaration of 'log4cpp::StringUtil::split' c:\CVS\0.3.3\log4cpp\src\StringUtil.hh(49) : see declaration of 'log4cpp::StringUtil::split' c:\CVS\0.3.3\log4cpp\src\StringUtil.cpp(45) : warning C4018: '<' : signed/unsigned mismatch [mdaniar] Possible workaround : Should both of them return unsigned int ? B. c:\CVS\0.3.3\log4cpp\include\log4cpp\Configurator.hh(21) : warning C4275: non dll-interface class 'std::runtime_error' used as base for dll-interface class 'log4cpp::ConfigureFailure' c:\Program Files\Microsoft Visual Studio .NET\Vc7\include\stdexcept(137) : see declaration of 'std::runtime_error' c:\CVS\0.3.3\log4cpp\include\log4cpp\Configurator.hh(21) : see declaration of 'log4cpp::ConfigureFailure' [mdaniar] Possible workaround : #pragma warning(disable : 4275) C. testPattern.cpp c:\CVS\0.3.3\log4cpp\tests\testPattern.cpp(16) : error C2039: 'cerr' : is not a member of 'std' c:\CVS\0.3.3\log4cpp\tests\testPattern.cpp(16) : error C2065: 'cerr' : undeclared identifier c:\CVS\0.3.3\log4cpp\tests\testPattern.cpp(16) : error C2296: '<<' : illegal, left operand has type ''unknown-type'' c:\CVS\0.3.3\log4cpp\tests\testPattern.cpp(16) : error C2297: '<<' : illegal, right operand has type 'char [20]' [mdaniar] Possible workaround : include #iostream in testPattern.cpp thanks, Mohamad --- Bastiaan Bakker <bas...@li...> wrote: > Hi Mohamad, > > Thanks for the quick report. > * The compile errors in PatternLayout.cpp are caused > by initializing > static constant strings at declaration point, which > GCC accepts, but is > not standards compliant C++. I think I should switch > to GCC 3.2 as > primary development compiler, as it gives a proper > warning for it when > compiling with '-pedantic'. > I've moved the definition of these strings outside > the class declaration > to fix the comile problem. > > * PortabilityImpl.cpp was not committed to CVS yet, > but it is not part > of 0.3.3: I added it after the 0.3.3 release. I > guess you checked out > CVS HEAD, rather than REL_0_3_3. I've added it now. > > * BasicConfigurator was misssing from both the MSVC > and BCB5 project > files. I've added it now. In the long term I like to > have a mechanism to > update them automatically if a file is added to the > automake files. > Having to update 6(!) project files for the addition > of one source file > is no fun. Suggestions or code to alleviate this > problem are very > welcome.... > > * MSVC7 compile problems: please mail them.... > > Thanks, > > Bastiaan > > > On Sun, 2002-10-27 at 13:22, Daniar, Mohamad wrote: > > Hi : > > Downloaded 0.3.3 through CVS, > > > > Got this error for log4cpp.lib, > > d:\log4cpp\src\patternlayout.cpp(127) : error > C2258: > > illegal pure syntax, must be '= 0' > > d:\log4cpp\src\patternlayout.cpp(127) : error > C2252: > > 'FORMAT_ISO8601' : pure specifier can only be > > specified for functions > > d:\log4cpp\src\patternlayout.cpp(128) : error > C2258: > > illegal pure syntax, must be '= 0' > > d:\log4cpp\src\patternlayout.cpp(128) : error > C2252: > > 'FORMAT_ABSOLUTE' : pure specifier can only be > > specified for functions > > d:\log4cpp\src\patternlayout.cpp(129) : error > C2258: > > illegal pure syntax, must be '= 0' > > d:\log4cpp\src\patternlayout.cpp(129) : error > C2252: > > 'FORMAT_DATE' : pure specifier can only be > specified > > for functions > > PortabilityImpl.cpp > > fatal error C1083: Cannot open source file: > > 'D:\log4cpp\src\PortabilityImpl.cpp': No such file > or > > directory > > > > Had to add BasicConfigurator.cpp / .hh in > log4cpp.dsp > > > > btw: > > Tried to compile it using Visual C++ 7, > > Seems like MS fix the std:: problem (no need to > > workaround) > > but there's some new warnings and error, will mail > > them if interested. > > > > > > thanks, > > > > > > Mohamad > > > > --- Bastiaan Bakker <bas...@li...> > > wrote: > > > Hi, > > > > > > I've put 0.3.3 on SourceForge. It's a relatively > > > small update to 0.3.2, > > > the two most important changes are: > > > * build fixes for MSVC. 0.3.3 introduces > > > PortabilityImpl.hh, an internal > > > header file for portibality stuff that should > not be > > > part of the API. It > > > contains aliases in namespace 'std' for the > > > functions in <cstlib> and > > > <cstring> we use but MSVC mistakenly puts in the > > > global namespace. > > > * a new PatternLayout implementation. It > preparses > > > the conversionpattern > > > into a vector of PatternComponents. This should > make > > > it speedier and > > > more flexible. PatternLayout now also support > > > formatting specifiers like > > > '%-5.5p'. > > > > > > Please report any bugs/problems through the > normal > > > channels (bug tracker > > > or mailing list). > > > > > > Cheers, > > > > > > Bastiaan > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.net email is sponsored by: ApacheCon, > > > November 18-21 in > > > Las Vegas (supported by COMDEX), the only Apache > > > event to be > > > fully supported by the ASF. > http://www.apachecon.com > > > _______________________________________________ > > > Log4cpp-devel mailing list > > > Log...@li... > > > > > > https://lists.sourceforge.net/lists/listinfo/log4cpp-devel > > > > > > __________________________________________________ > > Do you Yahoo!? > > Y! Web Hosting - Let the expert host your web site > > http://webhosting.yahoo.com/ > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: ApacheCon, > November 18-21 in > > Las Vegas (supported by COMDEX), the only Apache > event to be > > fully supported by the ASF. > http://www.apachecon.com > > _______________________________________________ > > Log4cpp-devel mailing list > > Log...@li... > > > https://lists.sourceforge.net/lists/listinfo/log4cpp-devel > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: ApacheCon, > November 18-21 in > Las Vegas (supported by COMDEX), the only Apache > event to be > fully supported by the ASF. http://www.apachecon.com > _______________________________________________ > Log4cpp-devel mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/log4cpp-devel __________________________________________________ Do you Yahoo!? Y! Web Hosting - Let the expert host your web site http://webhosting.yahoo.com/ |
From: Bastiaan B. <bas...@li...> - 2002-10-27 23:27:40
|
Hi Mohamad, Thanks for the quick report. * The compile errors in PatternLayout.cpp are caused by initializing static constant strings at declaration point, which GCC accepts, but is not standards compliant C++. I think I should switch to GCC 3.2 as primary development compiler, as it gives a proper warning for it when compiling with '-pedantic'. I've moved the definition of these strings outside the class declaration to fix the comile problem. * PortabilityImpl.cpp was not committed to CVS yet, but it is not part of 0.3.3: I added it after the 0.3.3 release. I guess you checked out CVS HEAD, rather than REL_0_3_3. I've added it now. * BasicConfigurator was misssing from both the MSVC and BCB5 project files. I've added it now. In the long term I like to have a mechanism to update them automatically if a file is added to the automake files. Having to update 6(!) project files for the addition of one source file is no fun. Suggestions or code to alleviate this problem are very welcome.... * MSVC7 compile problems: please mail them.... Thanks, Bastiaan On Sun, 2002-10-27 at 13:22, Daniar, Mohamad wrote: > Hi : > Downloaded 0.3.3 through CVS, > > Got this error for log4cpp.lib, > d:\log4cpp\src\patternlayout.cpp(127) : error C2258: > illegal pure syntax, must be '= 0' > d:\log4cpp\src\patternlayout.cpp(127) : error C2252: > 'FORMAT_ISO8601' : pure specifier can only be > specified for functions > d:\log4cpp\src\patternlayout.cpp(128) : error C2258: > illegal pure syntax, must be '= 0' > d:\log4cpp\src\patternlayout.cpp(128) : error C2252: > 'FORMAT_ABSOLUTE' : pure specifier can only be > specified for functions > d:\log4cpp\src\patternlayout.cpp(129) : error C2258: > illegal pure syntax, must be '= 0' > d:\log4cpp\src\patternlayout.cpp(129) : error C2252: > 'FORMAT_DATE' : pure specifier can only be specified > for functions > PortabilityImpl.cpp > fatal error C1083: Cannot open source file: > 'D:\log4cpp\src\PortabilityImpl.cpp': No such file or > directory > > Had to add BasicConfigurator.cpp / .hh in log4cpp.dsp > > btw: > Tried to compile it using Visual C++ 7, > Seems like MS fix the std:: problem (no need to > workaround) > but there's some new warnings and error, will mail > them if interested. > > > thanks, > > > Mohamad > > --- Bastiaan Bakker <bas...@li...> > wrote: > > Hi, > > > > I've put 0.3.3 on SourceForge. It's a relatively > > small update to 0.3.2, > > the two most important changes are: > > * build fixes for MSVC. 0.3.3 introduces > > PortabilityImpl.hh, an internal > > header file for portibality stuff that should not be > > part of the API. It > > contains aliases in namespace 'std' for the > > functions in <cstlib> and > > <cstring> we use but MSVC mistakenly puts in the > > global namespace. > > * a new PatternLayout implementation. It preparses > > the conversionpattern > > into a vector of PatternComponents. This should make > > it speedier and > > more flexible. PatternLayout now also support > > formatting specifiers like > > '%-5.5p'. > > > > Please report any bugs/problems through the normal > > channels (bug tracker > > or mailing list). > > > > Cheers, > > > > Bastiaan > > > > > > > > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: ApacheCon, > > November 18-21 in > > Las Vegas (supported by COMDEX), the only Apache > > event to be > > fully supported by the ASF. http://www.apachecon.com > > _______________________________________________ > > Log4cpp-devel mailing list > > Log...@li... > > > https://lists.sourceforge.net/lists/listinfo/log4cpp-devel > > > __________________________________________________ > Do you Yahoo!? > Y! Web Hosting - Let the expert host your web site > http://webhosting.yahoo.com/ > > > ------------------------------------------------------- > This SF.net email is sponsored by: ApacheCon, November 18-21 in > Las Vegas (supported by COMDEX), the only Apache event to be > fully supported by the ASF. http://www.apachecon.com > _______________________________________________ > Log4cpp-devel mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/log4cpp-devel |
From: Daniar, M. <da...@ya...> - 2002-10-27 13:22:06
|
Just want to clarify, Missing BasicConfigurator.cpp / .hh has no relation with the errors bellow, It gives error in testpatterns dsp regards, Mohamad --- "Daniar, Mohamad" <da...@ya...> wrote: > Hi : > Downloaded 0.3.3 through CVS, > > Got this error for log4cpp.lib, > d:\log4cpp\src\patternlayout.cpp(127) : error C2258: > illegal pure syntax, must be '= 0' > d:\log4cpp\src\patternlayout.cpp(127) : error C2252: > 'FORMAT_ISO8601' : pure specifier can only be > specified for functions > d:\log4cpp\src\patternlayout.cpp(128) : error C2258: > illegal pure syntax, must be '= 0' > d:\log4cpp\src\patternlayout.cpp(128) : error C2252: > 'FORMAT_ABSOLUTE' : pure specifier can only be > specified for functions > d:\log4cpp\src\patternlayout.cpp(129) : error C2258: > illegal pure syntax, must be '= 0' > d:\log4cpp\src\patternlayout.cpp(129) : error C2252: > 'FORMAT_DATE' : pure specifier can only be specified > for functions > PortabilityImpl.cpp > fatal error C1083: Cannot open source file: > 'D:\log4cpp\src\PortabilityImpl.cpp': No such file > or > directory > > Had to add BasicConfigurator.cpp / .hh in > log4cpp.dsp > > btw: > Tried to compile it using Visual C++ 7, > Seems like MS fix the std:: problem (no need to > workaround) > but there's some new warnings and error, will mail > them if interested. > > > thanks, > > > Mohamad > > --- Bastiaan Bakker <bas...@li...> > wrote: > > Hi, > > > > I've put 0.3.3 on SourceForge. It's a relatively > > small update to 0.3.2, > > the two most important changes are: > > * build fixes for MSVC. 0.3.3 introduces > > PortabilityImpl.hh, an internal > > header file for portibality stuff that should not > be > > part of the API. It > > contains aliases in namespace 'std' for the > > functions in <cstlib> and > > <cstring> we use but MSVC mistakenly puts in the > > global namespace. > > * a new PatternLayout implementation. It preparses > > the conversionpattern > > into a vector of PatternComponents. This should > make > > it speedier and > > more flexible. PatternLayout now also support > > formatting specifiers like > > '%-5.5p'. > > > > Please report any bugs/problems through the normal > > channels (bug tracker > > or mailing list). > > > > Cheers, > > > > Bastiaan > > > > > > > > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: ApacheCon, > > November 18-21 in > > Las Vegas (supported by COMDEX), the only Apache > > event to be > > fully supported by the ASF. > http://www.apachecon.com > > _______________________________________________ > > Log4cpp-devel mailing list > > Log...@li... > > > https://lists.sourceforge.net/lists/listinfo/log4cpp-devel > > > __________________________________________________ > Do you Yahoo!? > Y! Web Hosting - Let the expert host your web site > http://webhosting.yahoo.com/ > > > ------------------------------------------------------- > This SF.net email is sponsored by: ApacheCon, > November 18-21 in > Las Vegas (supported by COMDEX), the only Apache > event to be > fully supported by the ASF. http://www.apachecon.com > _______________________________________________ > Log4cpp-devel mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/log4cpp-devel __________________________________________________ Do you Yahoo!? Y! Web Hosting - Let the expert host your web site http://webhosting.yahoo.com/ |
From: Daniar, M. <da...@ya...> - 2002-10-27 12:22:24
|
Hi : Downloaded 0.3.3 through CVS, Got this error for log4cpp.lib, d:\log4cpp\src\patternlayout.cpp(127) : error C2258: illegal pure syntax, must be '= 0' d:\log4cpp\src\patternlayout.cpp(127) : error C2252: 'FORMAT_ISO8601' : pure specifier can only be specified for functions d:\log4cpp\src\patternlayout.cpp(128) : error C2258: illegal pure syntax, must be '= 0' d:\log4cpp\src\patternlayout.cpp(128) : error C2252: 'FORMAT_ABSOLUTE' : pure specifier can only be specified for functions d:\log4cpp\src\patternlayout.cpp(129) : error C2258: illegal pure syntax, must be '= 0' d:\log4cpp\src\patternlayout.cpp(129) : error C2252: 'FORMAT_DATE' : pure specifier can only be specified for functions PortabilityImpl.cpp fatal error C1083: Cannot open source file: 'D:\log4cpp\src\PortabilityImpl.cpp': No such file or directory Had to add BasicConfigurator.cpp / .hh in log4cpp.dsp btw: Tried to compile it using Visual C++ 7, Seems like MS fix the std:: problem (no need to workaround) but there's some new warnings and error, will mail them if interested. thanks, Mohamad --- Bastiaan Bakker <bas...@li...> wrote: > Hi, > > I've put 0.3.3 on SourceForge. It's a relatively > small update to 0.3.2, > the two most important changes are: > * build fixes for MSVC. 0.3.3 introduces > PortabilityImpl.hh, an internal > header file for portibality stuff that should not be > part of the API. It > contains aliases in namespace 'std' for the > functions in <cstlib> and > <cstring> we use but MSVC mistakenly puts in the > global namespace. > * a new PatternLayout implementation. It preparses > the conversionpattern > into a vector of PatternComponents. This should make > it speedier and > more flexible. PatternLayout now also support > formatting specifiers like > '%-5.5p'. > > Please report any bugs/problems through the normal > channels (bug tracker > or mailing list). > > Cheers, > > Bastiaan > > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: ApacheCon, > November 18-21 in > Las Vegas (supported by COMDEX), the only Apache > event to be > fully supported by the ASF. http://www.apachecon.com > _______________________________________________ > Log4cpp-devel mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/log4cpp-devel __________________________________________________ Do you Yahoo!? Y! Web Hosting - Let the expert host your web site http://webhosting.yahoo.com/ |
From: Bastiaan B. <bas...@li...> - 2002-10-27 00:21:13
|
Hi, I've put 0.3.3 on SourceForge. It's a relatively small update to 0.3.2, the two most important changes are: * build fixes for MSVC. 0.3.3 introduces PortabilityImpl.hh, an internal header file for portibality stuff that should not be part of the API. It contains aliases in namespace 'std' for the functions in <cstlib> and <cstring> we use but MSVC mistakenly puts in the global namespace. * a new PatternLayout implementation. It preparses the conversionpattern into a vector of PatternComponents. This should make it speedier and more flexible. PatternLayout now also support formatting specifiers like '%-5.5p'. Please report any bugs/problems through the normal channels (bug tracker or mailing list). Cheers, Bastiaan |
From: Bastiaan B. <Bas...@li...> - 2002-10-25 15:33:48
|
On Fri, 2002-10-25 at 16:10, Daniar, Mohamad wrote: > Yes, > I got the same problem, > I have to remove std:: namespace from all of those function, > it fixed the error. Well, it doesn't fix the error, it works around it: the C++ standard requires <cstdlib> to provide std::getenv() for example. Removing the 'std::' namespace would break builds with compliant compilers. I'll add workarounds in Portability.hh. Cheers, Bastiaan > > thanks, > > Mohamad > > ----- Original Message ----- > From: "Bastiaan Bakker" <Bas...@li...> > To: <log...@li...> > Sent: Friday, October 25, 2002 4:44 AM > Subject: [Log4cpp-devel] 0.3.2 msvc6 compile error (bug #628211) > > > Hi, > > Someone reported the compilation problems included below. The missing > '#include <string>' in MSThreads.hh already has been reported and fixed. > The others haven't been reported yet. Does anyone else have these > compilation problems on MSVC 6.0? Are they caused by a broken compiler > environment of the reporter or bugs in MSVC itself or a result of the > missing #include? (The mention functions *are* a member of the std > namespace). > > Thanks, > > Bastiaan > > > Build fails on MSVC 6.0 for v 0.3.2 > Building the static (log4cpp) project under MSVC 6.0 > gives the following errors: > > d:\projects\3rdparty\aa\log4cpp-0.3.2\include\log4cpp\threading\msthreads.hh > (46) > : error C2653: 'std' : is not a class or namespace name > > > d:\projects\3rdparty\aa\log4cpp-0.3.2\src\remotesyslogappender.cpp(148) > : error C2039: 'memmove' : is not a member of 'std' > > d:\projects\3rdparty\aa\log4cpp-0.3.2\src\priority.cpp(46) > : error C2039: 'strtoul' : is not a member of 'std' > > > d:\projects\3rdparty\aa\log4cpp-0.3.2\src\properties.cpp(83) > : error C2039: 'atoi' : is not a member of 'std' > d:\projects\3rdparty\aa\log4cpp-0.3.2\src\properties.cpp(124) > : error C2039: 'getenv' : is not a member of 'std' > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: Influence the future > of Java(TM) technology. Join the Java Community > Process(SM) (JCP(SM)) program now. > http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en > _______________________________________________ > Log4cpp-devel mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/log4cpp-devel > > > > ------------------------------------------------------- > This sf.net email is sponsored by: Influence the future > of Java(TM) technology. Join the Java Community > Process(SM) (JCP(SM)) program now. > http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en > _______________________________________________ > Log4cpp-devel mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/log4cpp-devel |
From: Daniar, M. <md...@pr...> - 2002-10-25 14:12:06
|
Yes, I got the same problem, I have to remove std:: namespace from all of those function, it fixed the error. thanks, Mohamad ----- Original Message ----- From: "Bastiaan Bakker" <Bas...@li...> To: <log...@li...> Sent: Friday, October 25, 2002 4:44 AM Subject: [Log4cpp-devel] 0.3.2 msvc6 compile error (bug #628211) Hi, Someone reported the compilation problems included below. The missing '#include <string>' in MSThreads.hh already has been reported and fixed. The others haven't been reported yet. Does anyone else have these compilation problems on MSVC 6.0? Are they caused by a broken compiler environment of the reporter or bugs in MSVC itself or a result of the missing #include? (The mention functions *are* a member of the std namespace). Thanks, Bastiaan Build fails on MSVC 6.0 for v 0.3.2 Building the static (log4cpp) project under MSVC 6.0 gives the following errors: d:\projects\3rdparty\aa\log4cpp-0.3.2\include\log4cpp\threading\msthreads.hh (46) : error C2653: 'std' : is not a class or namespace name d:\projects\3rdparty\aa\log4cpp-0.3.2\src\remotesyslogappender.cpp(148) : error C2039: 'memmove' : is not a member of 'std' d:\projects\3rdparty\aa\log4cpp-0.3.2\src\priority.cpp(46) : error C2039: 'strtoul' : is not a member of 'std' d:\projects\3rdparty\aa\log4cpp-0.3.2\src\properties.cpp(83) : error C2039: 'atoi' : is not a member of 'std' d:\projects\3rdparty\aa\log4cpp-0.3.2\src\properties.cpp(124) : error C2039: 'getenv' : is not a member of 'std' ------------------------------------------------------- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en _______________________________________________ Log4cpp-devel mailing list Log...@li... https://lists.sourceforge.net/lists/listinfo/log4cpp-devel |
From: Bastiaan B. <Bas...@li...> - 2002-10-25 08:47:41
|
Hi, Someone reported the compilation problems included below. The missing '#include <string>' in MSThreads.hh already has been reported and fixed. The others haven't been reported yet. Does anyone else have these compilation problems on MSVC 6.0? Are they caused by a broken compiler environment of the reporter or bugs in MSVC itself or a result of the missing #include? (The mention functions *are* a member of the std namespace). Thanks, Bastiaan Build fails on MSVC 6.0 for v 0.3.2 Building the static (log4cpp) project under MSVC 6.0 gives the following errors: d:\projects\3rdparty\aa\log4cpp-0.3.2\include\log4cpp\threading\msthreads.hh(46) : error C2653: 'std' : is not a class or namespace name d:\projects\3rdparty\aa\log4cpp-0.3.2\src\remotesyslogappender.cpp(148) : error C2039: 'memmove' : is not a member of 'std' d:\projects\3rdparty\aa\log4cpp-0.3.2\src\priority.cpp(46) : error C2039: 'strtoul' : is not a member of 'std' d:\projects\3rdparty\aa\log4cpp-0.3.2\src\properties.cpp(83) : error C2039: 'atoi' : is not a member of 'std' d:\projects\3rdparty\aa\log4cpp-0.3.2\src\properties.cpp(124) : error C2039: 'getenv' : is not a member of 'std' |
From: Bastiaan B. <Bas...@li...> - 2002-10-10 15:50:31
|
On Wed, 2002-10-09 at 21:19, Mohamad Daniar wrote: > Try to > #include <string> > > in MSThreads.hh Has been committed to CVS, thanks. > > btw, > any idea when will the stable version updated ? Actually I've been too lazy to work on the stable branch, as I exclusively use the development branch myself. If someone volunteers to maintain the stable branch, please be my guest. Else I think I'll wrap up some open issues in stable, release 0.2.8 and close the branch. Cheers, Bastiaan > > Mohamad > > ----- Original Message ----- > From: "msew" <> > To: <log...@li...> > Sent: Wednesday, October 09, 2002 2:53 PM > Subject: [Log4cpp-devel] compile errors in 0.3.2 (std not found) > > > > when compiling 0.3.2 in visual studio I get > > > > > c:\depot_vanguard\coding\source\Vanguard\xlib\Log4cpp\include\log4cpp\thread > ing\MSThreads.hh(58) > > : error C2653: 'std' : is not a class or namespace name > > > c:\depot_vanguard\coding\source\Vanguard\xlib\Log4cpp\include\log4cpp\thread > ing\MSThreads.hh(58) > > : error C2146: syntax error : missing ';' before identifier 'getThreadId' > > > c:\depot_vanguard\coding\source\Vanguard\xlib\Log4cpp\include\log4cpp\thread > ing\MSThreads.hh(58) > > : error C2501: 'string' : missing storage-class or type specifiers > > > > > > > > shouldn't namespace std be automagically included in the default visual > > studio default setup? > > > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > _______________________________________________ > > Log4cpp-devel mailing list > > Log...@li... > > https://lists.sourceforge.net/lists/listinfo/log4cpp-devel > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Log4cpp-devel mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/log4cpp-devel |
From: Mohamad D. <md...@pr...> - 2002-10-09 19:20:11
|
Try to #include <string> in MSThreads.hh btw, any idea when will the stable version updated ? Mohamad ----- Original Message ----- From: "msew" <> To: <log...@li...> Sent: Wednesday, October 09, 2002 2:53 PM Subject: [Log4cpp-devel] compile errors in 0.3.2 (std not found) > when compiling 0.3.2 in visual studio I get > > c:\depot_vanguard\coding\source\Vanguard\xlib\Log4cpp\include\log4cpp\thread ing\MSThreads.hh(58) > : error C2653: 'std' : is not a class or namespace name > c:\depot_vanguard\coding\source\Vanguard\xlib\Log4cpp\include\log4cpp\thread ing\MSThreads.hh(58) > : error C2146: syntax error : missing ';' before identifier 'getThreadId' > c:\depot_vanguard\coding\source\Vanguard\xlib\Log4cpp\include\log4cpp\thread ing\MSThreads.hh(58) > : error C2501: 'string' : missing storage-class or type specifiers > > > > shouldn't namespace std be automagically included in the default visual > studio default setup? > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Log4cpp-devel mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/log4cpp-devel |
From: msew <ms...@ev...> - 2002-10-09 18:56:01
|
At 16:07 02/10/05 +0200, Bastiaan Bakker wrote: > > testPropConfig > > I think this project was still missing. I grabbed from cvs :-) |
From: msew <ms...@ev...> - 2002-10-09 18:53:28
|
when compiling 0.3.2 in visual studio I get c:\depot_vanguard\coding\source\Vanguard\xlib\Log4cpp\include\log4cpp\threading\MSThreads.hh(58) : error C2653: 'std' : is not a class or namespace name c:\depot_vanguard\coding\source\Vanguard\xlib\Log4cpp\include\log4cpp\threading\MSThreads.hh(58) : error C2146: syntax error : missing ';' before identifier 'getThreadId' c:\depot_vanguard\coding\source\Vanguard\xlib\Log4cpp\include\log4cpp\threading\MSThreads.hh(58) : error C2501: 'string' : missing storage-class or type specifiers shouldn't namespace std be automagically included in the default visual studio default setup? |