log4cpp-devel — technical discussions about the development of log4cpp

Re: [Log4cpp-devel] A note regarding Shibboleth use of log4cpp

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

> I have commited localtime_r fix and pthread support. I check build on
> Fedora 7. Please check on non Linux to be sure that everything is OK. I am
> as blind with all this autotools, configure and others so mistakes are
> assumed.

Well, there are a couple of issues:

Not all of my changes are there, and all of them were done for a reason. For
example, the language isn't correctly set to C or C++ in the right places to
ensure the tests run correctly. The existing script uses C++ prematurely,
which fails on most platforms, rather that starting with C and then
switching for the C++ tests.

Lastly, and more importantly, I don't believe my use of the thread macros is
compatible with the existing macros that are still being called:

BB_CHECK_OMNITHREADS
BB_CHECK_PTHREADS

The second one probably overlaps and the first one would probably break. I
commented them out in my version because I don't know what OMNITHREADS is
and my code can't allow it anyway, so I didn't need to support it.

If you're trying to support that and pthreads properly, there's more work
required, and some testing that I couldn't do. If not, you just comment them
out and it requires pthreads be used. The current script with part of my
changes is already blocking use of any option other than pthreads, in fact,
which is not necessarily what you want.

For reference, the diff I ran is below with the changes that matter left in.

-- Scott

# diff configure.in ~/src/log4cpp-0.3.5rc1/configure.in 
49a50,54
> if test "$GCC" = "yes" ; then
>     CFLAGS="$GCC_CFLAGS"
>     CXXFLAGS="$GCC_CXXFLAGS"
> fi
> 
51c56
< AC_LANG(C++)
---
> AC_LANG(C)
61d65
< AC_CXX_HAVE_SSTREAM
89a89,92
> AC_LANG(C++)
> 
> AC_CXX_HAVE_SSTREAM
> 
103,104c106,107
< BB_CHECK_OMNITHREADS
< BB_CHECK_PTHREADS
---
> #BB_CHECK_OMNITHREADS
> #BB_CHECK_PTHREADS

Re: [Log4cpp-devel] A note regarding Shibboleth use of log4cpp

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

Hello, Scott!
You wrote to <log...@li...> on Fri, 17 Aug 2007 
12:35:47 -0400:

SC> There are various changes to fix threading but also to correct C++
SC> build issues on platforms where using gcc as a link front-end for C++
SC> is not possible (i.e. everywhere but Linux).

SC> If there's a specific change that is controversial, I can go back and
SC> determine what the change was for, I just don't have a list offhand as
SC> it was many years ago.

    I have commited localtime_r fix and pthread support. I check build on 
Fedora 7. Please check on non Linux to be sure that everything is OK. I am 
as blind with all this autotools, configure and others so mistakes are 
assumed.

With best regards, Konstantin Litvinenko.  E-mail: 
Kon...@ma... 

Re: [Log4cpp-devel] A note regarding Shibboleth use of log4cpp

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

>  SC> - a broken autotools script that failed to set the proper flags on
>  SC> Solaris and other platforms
> 
>      Waiting patch that fix this issue from Russ Allbery.

If you don't have it yet, I can provide my copy of the configure script, or
you can get it from inside the old package I posted:

http://shibboleth.internet2.edu/downloads/log4cpp-0.3.5rc1.tar.gz

There are various changes to fix threading but also to correct C++ build
issues on platforms where using gcc as a link front-end for C++ is not
possible (i.e. everywhere but Linux).

If there's a specific change that is controversial, I can go back and
determine what the change was for, I just don't have a list offhand as it
was many years ago.
 
-- Scott

Re: [Log4cpp-devel] A note regarding Shibboleth use of log4cpp

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

Hello, Scott!
You wrote to <log...@li...> on Thu, 16 Aug 2007 
23:28:11 -0400:

 SC> A long time back, pre-2004 certainly, we realized that log4cpp was
 SC> extremely broken under even rudimentary threaded conditions. I traced
 SC> this problem to two main sources:

 SC> - use of the non-threadsafe localtime function

    Fixed in my local copy.

 SC> - a broken autotools script that failed to set the proper flags on
 SC> Solaris and other platforms

     Waiting patch that fix this issue from Russ Allbery.

 SC> (To my knowledge, the NDC class was always threadsafe (it uses
 SC> thread-local-storage), in contrast to some recent comments here. I
 SC> can't explain that, but I think the concerns there are wrong.)

    You are right :) My previuos investigation was wrong. I have reviewed 
one more time NDC and PThread code and now realize that everything is OK 
with it.

With best regards, Konstantin Litvinenko. 

[Log4cpp-devel] A note regarding Shibboleth use of log4cpp

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

I know there's been some discussion and some confusion over this topic, so
now that I realized there's a mailing list with some traffic rather than the
dead SourceForge forums, I can hopefully clarify and contribute.

A long time back, pre-2004 certainly, we realized that log4cpp was extremely
broken under even rudimentary threaded conditions. I traced this problem to
two main sources:

- use of the non-threadsafe localtime function

- a broken autotools script that failed to set the proper flags on Solaris
and other platforms

One or two other small bugs were fixed around the same time in response to
some other issues I ran across, which I think have subsequently been fixed
in the trunk, just not in quite the same way, but that's fine.

At the time, I had already packaged up my own build because I could not
convince the original author to fix the libtool scripts to support Solaris.
This was discouraging to me and I simply didn't have the time to argue about
it, I needed a working tree so I built one. The threading bugs came up after
that.

(To my knowledge, the NDC class was always threadsafe (it uses
thread-local-storage), in contrast to some recent comments here. I can't
explain that, but I think the concerns there are wrong.)

Anyway, the project by that time was really dead, and I just didn't have a
choice. Now that it seems to be active again, I hope that we can get these
patches applied and get a new release out.

-- Scott

Re: [Log4cpp-devel] short information about upcoming release

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

Hello, waffel!
You wrote to <log...@li...> on Mon, 13 Aug 2007 
20:08:49 +0200:

 w> I think Konstantin is right and we should create a minor version because
 w> we have some new features and any bugfixes.

    We have bugfixes. I have fixed appenderMap initinalization bug. Also I 
have fixed localtime issue, but these changes only in my local copy because 
I wait until Russ Allbery send me a patch that fix pthread flags.

 w> I'll wait a little bit about the problem with the cross compiling stuff
 w> for ARM.

 w> @Konstantin: many thanks for your support!

You are welcome ;)

With best regards, Konstantin Litvinenko. 

Re: [Log4cpp-devel] Fw: cross compile log4cpp for ARM

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

Hello, Marcel!
You wrote to <log...@li...> on Mon, 13 Aug 2007 
08:29:25 -0700 (PDT):

 MM> I also attached the config.log file for additional info

This is your error

/usr/local/U-Boot/U-Boot/toolchain/bin/../lib/gcc-lib/arm-linux-uclibc/3.3.3/../../../../arm-linux-uclibc/bin/ld: 
warning: ld-uClibc.so.0, needed by /home/mem/LxNETES/LxNETES/lib//libc.so, 
not found (try using -rpath or -rpath-link)
/usr/local/U-Boot/U-Boot/toolchain/bin/../lib/gcc-lib/arm-linux-uclibc/3.3.3/../../../../arm-linux-uclibc/lib/crt1.o(.text+0x20): 
In function `_start':
: undefined reference to `__uClibc_start_main'
/home/mem/LxNETES/LxNETES/lib//libc.so: undefined reference to 
`__libc_stack_end'
collect2: ld returned 1 exit status

I think you should write simple makefile and build simple executable file to 
figure out what flags you need to build a minimal program. Than you should 
pass those flags to configure script.

With best regards, Konstantin Litvinenko. 

[Log4cpp-devel] short information about upcoming release

[waffel <wa...@ho...>]

Hi,

sorry for this huge delay. But my ISP was down for nearly 2 weeks and 
than I had my year holidays. Now I'am back at home and hope my IPS is 
stabe so I can create the next release.

I think Konstantin is right and we should create a minor version because 
we have some new features and any bugfixes.

I'll wait a little bit about the problem with the cross compiling stuff 
for ARM.

@Konstantin: many thanks for your support!

@all others: Thank you for posting on the maillinglist, testing and 
submitting patches!

Hope we can push out the next release with these nice new features and 
increasing the stability more than once.

Regards,

- waffel

Re: [Log4cpp-devel] cross compile log4cpp for ARM

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

Hello, Marcel!
You wrote to <log...@li...> on Sun, 12 Aug 2007 
16:34:08 -0700 (PDT):

 MM> Hello, I am trying to cross compile the log4cpp library (version 0.3.5)

[Sorry, skipped]

 MM> error output:
 MM> checking for gcc... arm-linux-gcc
 MM> checking for C compiler default output file name... configure: error: C
 MM> compiler cannot create executables See `config.log' for more details.

 MM> This makes sense, since ARM executables are not the same as for intel.
 MM> How do I resolve this problem so that i can also compile the library to
 MM> tun on an arm system?

    I think you should post 'config.log.' to give more information.

With best regards, Konstantin Litvinenko. 

[Log4cpp-devel] cross compile log4cpp for ARM

[Marcel M. <ma...@ya...>]

Hello, I am trying to cross compile the log4cpp library (version 0.3.5) for=
 an arm architecture. I am invoking the ./configure script with the followi=
ng options, but always the an error (see below)=0A=0A./configure --prefix=
=3D/home/mem/LxNETES/rhapsody/liblogArm/ --with-pthread CC=3Darm-linux-gcc =
CPPFLAGS=3D-I/home/mem/LxNETES/LxNETES/include/ LDFLAGS=3D-L/home/mem/LxNET=
ES/LxNETES/lib/=0A(I have also trid: CC=3Darm-linux-gcc CPPFLAGS=3D-I/home/=
mem/LxNETES/LxNETES/include/ LDFLAGS=3D-L/home/mem/LxNETES/LxNETES/lib/ ./c=
onfigure --prefix=3D/home/mem/LxNETES/rhapsody/liblogArm/ --with-pthread  b=
ut also without success)=0A=0Aerror output:=0Achecking for gcc... arm-linux=
-gcc=0Achecking for C compiler default output file name... configure: error=
: C compiler cannot create executables=0ASee `config.log' for more details.=
=0A=0AThis makes sense, since ARM executables are not the same as for intel=
.  How do I resolve this problem so that i can also compile the library to =
tun on an arm system?=0A=0AThanks greatly for the help=0A=0AMarcel=0A=0A=0A=
=0A=0A=0A       =0A________________________________________________________=
____________________________=0ABuilding a website is a piece of cake. Yahoo=
! Small Business gives you all the tools to get online.=0Ahttp://smallbusin=
ess.yahoo.com/webhosting 

Re: [Log4cpp-devel] New release

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

Hello, fb...@fr...!
You wrote to "Konstantin Litvinenko" <Kon...@ma...> on 
Fri, 27 Jul 2007 11:56:43 +0200:

 f> could you take a look to:
 f> https://spaces.internet2.edu/display/SHIB/Log4Cpp

    I have looked on this and found that there is no differencies between 
log4cpp CVS HEAD and shibboleth.log4cpp. I have commited bug fix for static 
initialization into head. Can you please check is CVS HEAD version?
    There only one thing I can tell is NDC usage in mutitheaded environment 
is NOT safe. To make it safe user must call log4cpp::getNDC() before any tow 
threads make simultaneously call to that function. That may be done in main 
or any other place where is only one thread of exceution that use 
log4cpp::NDC.

With best regards, Konstantin Litvinenko. 

Re: [Log4cpp-devel] New release

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

Hi konstantin, all,

> I have looked the bug report and don't think it is threading issue too. I
> think we have some problems with NDC. I will look on it closely on weekend.

thanks !

could you take a look to:
https://spaces.internet2.edu/display/SHIB/Log4Cpp

> During the course of Shibboleth development, the original author orphaned
> the library and a set of patches was locally applied to produce a custom
> package to correct some thread safety and shutdown issues in the code. The
> project has since revived but a sync-up has not yet occurred. You MUST use
> the Internet2-supplied version or you will not have a reliable package.
> The locally produced source package is available at
> http://shibboleth.internet2.edu/downloads/log4cpp-0.3.5rc1.tar.gz

i will ping shibboleth guys, it could be nice to merge the changes and do the
sync.

cheers,

Fathi

Re: [Log4cpp-devel] New release

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

Hello, Fathi!
You wrote to <log...@li...> on Thu, 26 Jul 2007 
22:03:15 +0200:

 FB> nice to hear that there's an upcoming log4cpp new release.
 FB> i received a bug report on the debian about a threading issue:
 FB> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432729

 FB> could someone take a look (waffel ? other?) at the submitted patch and
 FB> commit it if it is ok before the official release.

 FB> namespace log4cpp {
 FB> -    Appender::AppenderMap* Appender::_allAppenders;
 FB>     threading::Mutex Appender::_appenderMapMutex;

 FB>     /* assume _appenderMapMutex locked */
 FB>     Appender::AppenderMap& Appender::_getAllAppenders() {
 FB> -        if (!_allAppenders)
 FB> -            _allAppenders = new Appender::AppenderMap();
 FB> -
 FB> +        static Appender::AppenderMap* _allAppenders = new
 FB> Appender::AppenderMap();
 FB>         return *_allAppenders;
 FB>     }


    I don't see why folks thinks that it is threading issue, but I see very, 
very strange bug with line

    Appender::AppenderMap* Appender::_allAppenders;

How it's works in current release I can't understand. This line should be

    Appender::AppenderMap* Appender::_allAppenders = 0;

I have looked the bug report and don't think it is threading issue too. I 
think we have some problems with NDC. I will look on it closely on weekend.

With best regards, Konstantin Litvinenko. 

Re: [Log4cpp-devel] New release

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

Hello, Fathi!
You wrote to <log...@li...> on Thu, 26 Jul 2007 
22:03:15 +0200:

 FB> nice to hear that there's an upcoming log4cpp new release.
 FB> i received a bug report on the debian about a threading issue:
 FB> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432729

 FB> could someone take a look (waffel ? other?) at the submitted patch and
 FB> commit it if it is ok before the official release.

 FB> namespace log4cpp {
 FB> -    Appender::AppenderMap* Appender::_allAppenders;
 FB>     threading::Mutex Appender::_appenderMapMutex;

 FB>     /* assume _appenderMapMutex locked */
 FB>     Appender::AppenderMap& Appender::_getAllAppenders() {
 FB> -        if (!_allAppenders)
 FB> -            _allAppenders = new Appender::AppenderMap();
 FB> -
 FB> +        static Appender::AppenderMap* _allAppenders = new
 FB> Appender::AppenderMap();
 FB>         return *_allAppenders;
 FB>     }


    I don't see why folks thinks that it is threading issue, but I see very, 
very strange bug with line

    Appender::AppenderMap* Appender::_allAppenders;

How it's works in current release I can't understand. This line should be

    Appender::AppenderMap* Appender::_allAppenders = 0;

I have looked the bug report and don't think it is threading issue too. I 
think we have some problems with NDC. I will look on it closely on weekend.

With best regards, Konstantin Litvinenko. 

[Log4cpp-devel] New release

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

hi all,

nice to hear that there's an upcoming log4cpp new release.
i received a bug report on the debian about a threading issue:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432729

could someone take a look (waffel ? other?) at the submitted patch and commit 
it if it is ok before the official release.

--- ./log4cpp-0.3.5-rc3/src/Appender.cpp    2002-10-27 
02:48:52.000000000 +0100
+++ ./log4cpp-0.3.5rc1/src/Appender.cpp    2004-10-26 22:08:28.000000000 
+0200
@@ -11,14 +11,11 @@
#include <log4cpp/Appender.hh>

namespace log4cpp {
-    Appender::AppenderMap* Appender::_allAppenders;
    threading::Mutex Appender::_appenderMapMutex;

    /* assume _appenderMapMutex locked */
    Appender::AppenderMap& Appender::_getAllAppenders() {
-        if (!_allAppenders)
-            _allAppenders = new Appender::AppenderMap();
-
+        static Appender::AppenderMap* _allAppenders = new 
Appender::AppenderMap();
        return *_allAppenders;
    }

cheers,

Fathi

[Log4cpp-devel] New release

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

Hello All!

    I have finished build for msvc 8.0, MinGW32 (gcc 3.4.2), borland 5.6.4 
and gcc 4.1.1 :) Everything seams to work. This is not a simple bugfix 
release because we added factories into codebase. So may be we should 
increase minor version?

Post here because have no response from waffel.

With best regards, Konstantin Litvinenko.

Re: [Log4cpp-devel] new small bugfix release

[waffel <wa...@ho...>]

Hi Konstantin,

Many thanks. I can wait until you are finished. Simple drop me an mail 
and I'll create the release.

Regards,

- waffel

Konstantin Litvinenko schrieb:
> Hello, waffel!
> You wrote to <log...@li...> on Wed, 27 Jun 2007
> 13:25:48 +0200:
>
> w> Hopfully with the new bugfix relaese, the compile problems are gone.
> w> Currently I'am only able to test it on my linux box. If there is anybody
> w> who can check the current cvs sources on a windows box or other linux
> w> systems (I'am using gentoo only)?
>
> Sorry for late response. I will test on msvc 8.0 and MinGW-5.1.3 tomorrow.
> For gcc 4.x.x in Fedora 6 I found some bugs, but now I do not have access to
> that compiler. I can test it on monday. Will you wait until there?
>
> With best regards, Konstantin Litvinenko. 
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Log4cpp-devel mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4cpp-devel
>   

Re: [Log4cpp-devel] new small bugfix release

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

Hello, waffel!
You wrote to <log...@li...> on Wed, 27 Jun 2007
13:25:48 +0200:

w> Hopfully with the new bugfix relaese, the compile problems are gone.
w> Currently I'am only able to test it on my linux box. If there is anybody
w> who can check the current cvs sources on a windows box or other linux
w> systems (I'am using gentoo only)?

Sorry for late response. I will test on msvc 8.0 and MinGW-5.1.3 tomorrow.
For gcc 4.x.x in Fedora 6 I found some bugs, but now I do not have access to
that compiler. I can test it on monday. Will you wait until there?

With best regards, Konstantin Litvinenko. 

[Log4cpp-devel] wiki account request

[<Ric...@Mc...>]

I would like to request a wiki account.

=20

Thanks in advance,

-Richard

=20

Richard Craighead, Principal Software Engineer * McAfee Inc

5000 Headquarters Drive, Plano, Texas 75024

972.963.7636 * ric...@mc...
<mailto:ric...@mc...>  * www.mcafee.com
<http://www.mcafee.com/>=20

=20

=20

=20

=20

=20

=20

[Log4cpp-devel] new small bugfix release

[waffel <wa...@ho...>]

Hi @all,

I will create after a long time another small bugfix release. For myself 
I have tried to build log4cpp from the current cvs sources and found a 
compiler problem which was easy to fix.

If there are any patches which are currently NOT applied to the cvs 
sources? I'll waiting the next two days before I create the release. If 
there are any patches, please send them to the maillinglist or create a 
bugtracker entry and assign them to me. I'll will have a look about the 
patches and apply them to the sources, after a short review.

Hopfully with the new bugfix relaese, the compile problems are gone. 
Currently I'am only able to test it on my linux box. If there is anybody 
who can check the current cvs sources on a windows box or other linux 
systems (I'am using gentoo only)?

Regards,

- waffel

[Log4cpp-devel] =?iso-8859-7?q?Re_=3A__Build_Error_=22=2E=2E/incl?= =?iso-8859-7?q?ude/log4cpp/Manipulator=2Ehh=3A29=3A_error=3A_extra_=A1=3B?= =?iso-8859-7?b?oiI=?=

[Philippe H. <phi...@ya...>]

Hello,=0A=0AIn Manipulator.hh, there is an extra ';' at line 29 after the '=
}' that closes the log4cpp namespace. =0AJust get rid of it and it should c=
ompile OK.=0A=0ABest regards,=0A=0APH=0A=0A----- Message d'origine ----=0AD=
e : Jan Klever <kl...@df...>=0A=C0 : log...@li...urceforge=
.net=0AEnvoy=E9 le : Lundi, 16 Avril 2007, 14h52mn 57s=0AObjet : [Log4cpp-d=
evel] Build Error "../include/log4cpp/Manipulator.hh:29: error: extra =91;=
=92"=0A=0AHi,=0A=0Ai am trying to build log4cpp-0.3.5rc3 under SLES10=0A- g=
cc 4.1.0=0A- gmake 3.80=0A- glibc 2.4=0A- kernel 2.6.16.21=0A=0AArguments t=
o configure:=0A./configure --disable-static --disable-doxygen=0A=0Amake run=
s into an error:=0A=0A g++ -DHAVE_CONFIG_H -I. -I. -I../include -I../includ=
e -g -O2 -Wall=0A-Wno-unused -pedantic -MT FileAppender.lo -MD -MP -MF=0A.d=
eps/FileAppender.Tpo -c FileAppender.cpp  -fPIC -DPIC -o=0A.libs/FileAppend=
er.o=0A../include/log4cpp/Manipulator.hh:29: error: extra =91;=92=0Amake[1]=
: *** [FileAppender.lo] Error 1=0Amake[1]: Leaving directory=0A`/services/s=
ource/build/log4cpp/log4cpp-0.3.5rc3/src'make: ***=0A[all-recursive] Error =
1=0A=0AAny clue?=0A=0AThanks=0AJan=0A=0A-- =0AJan Klever (PKI Team), DFN-CE=
RT Services GmbH=0A=0ADFN-CERT Services GmbH, https://www.dfn-cert.de, Phon=
e +49 40 808077-555=0ASitz / Register: Hamburg, AG Hamburg, HRB 88805, Ust-=
IdNr.: DE 232129737=0A=0A=0A-----------------------------------------------=
--------------------------=0AThis SF.net email is sponsored by DB2 Express=
=0ADownload DB2 Express C - the FREE version of DB2 express and take=0Acont=
rol of your XML. No limits. Just data. Click to get it now.=0Ahttp://source=
forge.net/powerbar/db2/=0A_______________________________________________=
=0ALog4cpp-devel mailing list=0AL...@li...=0Ahttps=
://lists.sourceforge.net/lists/listinfo/log4cpp-devel=0A=0A=0A=0A=0A=0A=0A=
=0A      =0A_______________________________________________________________=
____________ =0AD=E9couvrez une nouvelle fa=E7on d'obtenir des r=E9ponses =
=E0 toutes vos questions ! =0AProfitez des connaissances, des opinions et d=
es exp=E9riences des internautes sur Yahoo! Questions/R=E9ponses =0Ahttp://=
fr.answers.yahoo.com

Re: [Log4cpp-devel] =?utf-8?q?Build_Error_=22=2E=2E/include/log4cpp/M?= =?utf-8?b?YW5pcHVsYXRvci5oaDoyOTogZXJyb3I6IGV4dHJhIOKAmDvigJki?=

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

Hello, Jan!
You wrote to <log...@li...> on Mon, 16 Apr 2007 
14:52:57 +0200:

 JK> i am trying to build log4cpp-0.3.5rc3 under SLES10
 JK> - gcc 4.1.0
 JK> - gmake 3.80
 JK> - glibc 2.4
 JK> - kernel 2.6.16.21

 JK> Arguments to configure:
 JK> ./configure --disable-static --disable-doxygen

 JK> make runs into an error:

 JK>  g++ -DHAVE_CONFIG_H -I. -I. -I../include -I../include -g -O2 -Wall
 JK> -Wno-unused -pedantic -MT FileAppender.lo -MD -MP -MF
 JK> .deps/FileAppender.Tpo -c FileAppender.cpp  -fPIC -DPIC -o
 JK> .libs/FileAppender.o
 JK> ../include/log4cpp/Manipulator.hh:29: error: extra ‘;’
 JK> make[1]: *** [FileAppender.lo] Error 1
 JK> make[1]: Leaving directory
 JK> `/services/source/build/log4cpp/log4cpp-0.3.5rc3/src'make: ***
 JK> [all-recursive] Error 1

 JK> Any clue?

    Take current cvs version please. This error was fixed in HEAD.

With best regards, Konstantin Litvinenko. 

[Log4cpp-devel] =?utf-8?q?Build_Error_=22=2E=2E/include/log4cpp/M?= =?utf-8?b?YW5pcHVsYXRvci5oaDoyOTogZXJyb3I6IGV4dHJhIOKAmDvigJki?=

[Jan K. <kl...@df...>]

Hi,

i am trying to build log4cpp-0.3.5rc3 under SLES10
- gcc 4.1.0
- gmake 3.80
- glibc 2.4
- kernel 2.6.16.21

Arguments to configure:
=2E/configure --disable-static --disable-doxygen

make runs into an error:

 g++ -DHAVE_CONFIG_H -I. -I. -I../include -I../include -g -O2 -Wall
-Wno-unused -pedantic -MT FileAppender.lo -MD -MP -MF
=2Edeps/FileAppender.Tpo -c FileAppender.cpp  -fPIC -DPIC -o
=2Elibs/FileAppender.o
=2E./include/log4cpp/Manipulator.hh:29: error: extra =E2=80=98;=E2=80=99
make[1]: *** [FileAppender.lo] Error 1
make[1]: Leaving directory
`/services/source/build/log4cpp/log4cpp-0.3.5rc3/src'make: ***
[all-recursive] Error 1

Any clue?

Thanks
Jan

--=20
Jan Klever (PKI Team), DFN-CERT Services GmbH

DFN-CERT Services GmbH, https://www.dfn-cert.de, Phone +49 40 808077-555
Sitz / Register: Hamburg, AG Hamburg, HRB 88805, Ust-IdNr.: DE 232129737

Re: [Log4cpp-devel] log4cpp and dlls

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

Hello, Lazy!
You wrote to <log...@li...> on Wed, 7 Mar 2007 
21:11:30 +0530:

 LL> I'm having some weird crashes when I'm using log4cpp over dll's.
 LL> I'm just using a single category (root), and every dll basically logs
 LL> on to that using the same macro.
 LL> What are the best practices in using log4cpp across dll's ?

    Every time I hear about log4cpp wierd crashes it is build problems. Make 
sure that all dlls use same runtime and same build ABI-compatible settings. 
log4cpp should be dll. Use depends.exe to see what runtime each dll use.

With best regards, Konstantin Litvinenko. 

[Log4cpp-devel] log4cpp and dlls

[Lazy L. <laz...@gm...>]

Hello everyone,

I'm having some weird crashes when I'm using log4cpp over dll's.
I'm just using a single category (root), and every dll basically logs
on to that using the same macro.

What are the best practices in using log4cpp across dll's ?

Thanks in advance ...