log4cpp-devel — technical discussions about the development of log4cpp

Re: [Log4cpp-devel] log4cpp 0.3.4b build system

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

Many Thanks Fathi :-)

after the cvs commit I will check it for myself and then we should create a minor release :-)

Regards,

waffel

> hi thomas,
> 
> already fixed :) thanks for the reply.
> 
> i finished to update debian package and it's now in the new queue :
> http://ftp-master.debian.org/new.html
> 
> i don't have updated on the cvs, but will do soon.
> 
> cheers,
> 
> fathi
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Log4cpp-devel mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4cpp-devel


---
This mail was sent with the Java email client Columba. Read more at http://columbamail.org

Re: [Log4cpp-devel] log4cpp 0.3.4b build system

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

hi thomas,

already fixed :) thanks for the reply.

i finished to update debian package and it's now in the new queue :
http://ftp-master.debian.org/new.html

i don't have updated on the cvs, but will do soon.

cheers,

fathi

Re: [Log4cpp-devel] log4cpp 0.3.4b build system

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

Hi Fathi,

sorry for the late answer :-(

You are welcome to update the build system. There is currently no plan to do such thinks. I don't know enaugh whats the main problems are but if the update helps us to get ride of these we should switch to the new tools.

Hope you have cvs access, else send me an request over sourceforge. We can also do a short guidline on our wiki to discuss such thinks before you commit the changes.

What do you think?

Regards,

- waffel

> hi all,
> 
> i would like to update build system 0.3.4b to current one :
> libtool1.5
> automake1.9
> autoconf 2.59
> 
> i've done an autoscan :
> 
> configure.in: warning: missing AC_CHECK_FUNCS([gethostbyaddr]) wanted by: 
> src/RemoteSyslogAppender.cpp:105
> configure.in: warning: missing AC_CHECK_FUNCS([gethostbyname]) wanted by: 
> src/RemoteSyslogAppender.cpp:83
> configure.in: warning: missing AC_CHECK_FUNCS([memchr]) wanted by: 
> src/snprintf.c:708
> configure.in: warning: missing AC_CHECK_FUNCS([memmove]) wanted by: 
> src/RemoteSyslogAppender.cpp:148
> configure.in: warning: missing AC_CHECK_FUNCS([memset]) wanted by: 
> src/snprintf.c:372
> configure.in: warning: missing AC_CHECK_FUNCS([socket]) wanted by: 
> src/RemoteSyslogAppender.cpp:115
> configure.in: warning: missing AC_CHECK_FUNCS([strchr]) wanted by: 
> src/snprintf.c:560
> configure.in: warning: missing AC_CHECK_FUNCS([strtol]) wanted by: 
> src/PortabilityImpl.hh:21
> configure.in: warning: missing AC_CHECK_FUNCS([strtoul]) wanted by: 
> src/Priority.cpp:46
> configure.in: warning: missing AC_CHECK_HEADERS([arpa/inet.h]) wanted by: 
> src/RemoteSyslogAppender.cpp:28
> configure.in: warning: missing AC_CHECK_HEADERS([fcntl.h]) wanted by: 
> src/RollingFileAppender.cpp:17
> configure.in: warning: missing AC_CHECK_HEADERS([netdb.h]) wanted by: 
> src/RemoteSyslogAppender.cpp:25
> configure.in: warning: missing AC_CHECK_HEADERS([netinet/in.h]) wanted by: 
> src/RemoteSyslogAppender.cpp:27
> configure.in: warning: missing AC_CHECK_HEADERS([sys/socket.h]) wanted by: 
> src/RemoteSyslogAppender.cpp:26
> configure.in: warning: missing AC_CHECK_HEADERS([sys/time.h]) wanted by: 
> src/TimeStamp.cpp:15
> configure.in: warning: missing AC_CHECK_HEADERS([sys/timeb.h]) wanted by: 
> src/TimeStamp.cpp:18
> configure.in: warning: missing AC_CHECK_HEADERS([syslog.h]) wanted by: 
> include/log4cpp/SyslogAppender.hh:16
> configure.in: warning: missing AC_C_CONST wanted by: src/snprintf.c:367
> configure.in: warning: missing AC_C_INLINE wanted by: 
> src/PortabilityImpl.hh:17
> configure.in: warning: missing AC_C_VOLATILE wanted by: 
> include/log4cpp/Category.hh:638
> configure.in: warning: missing AC_FUNC_ERROR_AT_LINE wanted by: 
> src/Category.cpp:347
> configure.in: warning: missing AC_FUNC_MALLOC wanted by: src/snprintf.c:428
> configure.in: warning: missing AC_FUNC_STRFTIME wanted by: 
> src/PatternLayout.cpp:166
> configure.in: warning: missing AC_HEADER_STDBOOL wanted by: 
> src/Appender.cpp:43
> configure.in: warning: missing AC_HEADER_TIME wanted by: src/TimeStamp.cpp:30
> configure.in: warning: missing AC_PROG_RANLIB wanted by: config/ltmain.sh:5029
> configure.in: warning: missing AC_STRUCT_TM wanted by: 
> src/PatternLayout.cpp:151
> configure.in: warning: missing AC_TYPE_MODE_T wanted by: 
> src/FileAppender.cpp:28
> configure.in: warning: missing AC_TYPE_OFF_T wanted by: 
> src/RollingFileAppender.cpp:73
> configure.in: warning: missing AC_TYPE_SIZE_T wanted by: src/snprintf.c:364
> 
> and an autoupdate, followed by an autoreconf -f -i :
> 
> /usr/share/aclocal/libmcrypt.m4:17: warning: underquoted definition of 
> AM_PATH_LIBMCRYPT
>   run info '(automake)Extending aclocal'
>   or see http://sources.redhat.com/automake/automake.html#Extending-aclocal
> /usr/share/aclocal/glib.m4:8: warning: underquoted definition of AM_PATH_GLIB
> Putting files in AC_CONFIG_AUX_DIR, `config'.
> /usr/share/aclocal/libmcrypt.m4:17: warning: underquoted definition of 
> AM_PATH_LIBMCRYPT
>   run info '(automake)Extending aclocal'
>   or see http://sources.redhat.com/automake/automake.html#Extending-aclocal
> /usr/share/aclocal/glib.m4:8: warning: underquoted definition of AM_PATH_GLIB
> configure.in:59: error: possibly undefined macro: AC_C_INT64_T
>       If this token and others are legitimate, please use m4_pattern_allow.
>       See the Autoconf documentation.
> configure.in:60: error: possibly undefined macro: AC_CXX_HAVE_SSTREAM
> configure.in:61: error: possibly undefined macro: AC_FUNC_SNPRINTF
> configure.in:94: error: possibly undefined macro: AC_CREATE_GENERIC_CONFIG
> configure.in:130: error: possibly undefined macro: AC_CREATE_PREFIX_CONFIG_H
> autoreconf: /usr/bin/autoconf failed with exit status: 1
> 
> who failed, any idea or guideline to follow for an updated build system for 
> 0.3.4b ?
> 
> cheers,
> 
> Fathi
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Log4cpp-devel mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4cpp-devel


---
This mail was sent with the Java email client Columba. Read more at http://columbamail.org

[Log4cpp-devel] Problem with link

[Anthony C. <an...@mb...>]

Hi,

I'm having troubles with log4cpp... when I compile my program, errors 
appear while linking. Here are the errors I got and the command I use to 
compile it :

g++ -O2 -g -o tun tun.cpp -lZThread -llog4cpp

/usr/lib/gcc-lib/i586-mandrake-linux-gnu/3.3.4/../../../liblog4cpp.so: 
undefined
 reference to `__gnu_cxx::__exchange_and_add(int volatile*, int)'
/usr/lib/gcc-lib/i586-mandrake-linux-gnu/3.3.4/../../../liblog4cpp.so: 
undefined
 reference to `std::_Rb_tree_decrement(std::_Rb_tree_node_base*)'
/usr/lib/gcc-lib/i586-mandrake-linux-gnu/3.3.4/../../../liblog4cpp.so: 
undefined
 reference to `std::_Rb_tree_increment(std::_Rb_tree_node_base const*)'
/usr/lib/gcc-lib/i586-mandrake-linux-gnu/3.3.4/../../../liblog4cpp.so: 
undefined
 reference to `std::_List_node_base::hook(std::_List_node_base*)'
/usr/lib/gcc-lib/i586-mandrake-linux-gnu/3.3.4/../../../liblog4cpp.so: 
undefined
 reference to `std::basic_string<char, std::char_traits<char>, 
std::allocator<ch
ar> >::_Rep::_S_empty_rep_storage'
/usr/lib/gcc-lib/i586-mandrake-linux-gnu/3.3.4/../../../liblog4cpp.so: 
undefined
 reference to `std::_Rb_tree_insert_and_rebalance(bool, 
std::_Rb_tree_node_base*
, std::_Rb_tree_node_base*, std::_Rb_tree_node_base&)'
/usr/lib/gcc-lib/i586-mandrake-linux-gnu/3.3.4/../../../liblog4cpp.so: 
undefined
 reference to 
`std::_Rb_tree_rebalance_for_erase(std::_Rb_tree_node_base*, std::
_Rb_tree_node_base&)'
/usr/lib/gcc-lib/i586-mandrake-linux-gnu/3.3.4/../../../liblog4cpp.so: 
undefined
 reference to `std::basic_ostream<char, std::char_traits<char> 
 >::seekp(long lon
g, std::_Ios_Seekdir)'
/usr/lib/gcc-lib/i586-mandrake-linux-gnu/3.3.4/../../../liblog4cpp.so: 
undefined
 reference to `std::_Rb_tree_increment(std::_Rb_tree_node_base*)'
/usr/lib/gcc-lib/i586-mandrake-linux-gnu/3.3.4/../../../liblog4cpp.so: 
undefined
 reference to `std::basic_string<char, std::char_traits<char>, 
std::allocator<ch
ar> >::_Rep::_S_create(unsigned, unsigned, std::allocator<char> const&)'
collect2: ld returned 1 exit status

To developp this program, I use log4cpp 0.3.4b, Mandriva 10.1 and g++ 
3.3.4. Do you know how I could resolve this problem ?

Thanks,

[Log4cpp-devel] log4cpp 0.3.4b build system

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

hi all,

i would like to update build system 0.3.4b to current one :
libtool1.5
automake1.9
autoconf 2.59

i've done an autoscan :

configure.in: warning: missing AC_CHECK_FUNCS([gethostbyaddr]) wanted by: 
src/RemoteSyslogAppender.cpp:105
configure.in: warning: missing AC_CHECK_FUNCS([gethostbyname]) wanted by: 
src/RemoteSyslogAppender.cpp:83
configure.in: warning: missing AC_CHECK_FUNCS([memchr]) wanted by: 
src/snprintf.c:708
configure.in: warning: missing AC_CHECK_FUNCS([memmove]) wanted by: 
src/RemoteSyslogAppender.cpp:148
configure.in: warning: missing AC_CHECK_FUNCS([memset]) wanted by: 
src/snprintf.c:372
configure.in: warning: missing AC_CHECK_FUNCS([socket]) wanted by: 
src/RemoteSyslogAppender.cpp:115
configure.in: warning: missing AC_CHECK_FUNCS([strchr]) wanted by: 
src/snprintf.c:560
configure.in: warning: missing AC_CHECK_FUNCS([strtol]) wanted by: 
src/PortabilityImpl.hh:21
configure.in: warning: missing AC_CHECK_FUNCS([strtoul]) wanted by: 
src/Priority.cpp:46
configure.in: warning: missing AC_CHECK_HEADERS([arpa/inet.h]) wanted by: 
src/RemoteSyslogAppender.cpp:28
configure.in: warning: missing AC_CHECK_HEADERS([fcntl.h]) wanted by: 
src/RollingFileAppender.cpp:17
configure.in: warning: missing AC_CHECK_HEADERS([netdb.h]) wanted by: 
src/RemoteSyslogAppender.cpp:25
configure.in: warning: missing AC_CHECK_HEADERS([netinet/in.h]) wanted by: 
src/RemoteSyslogAppender.cpp:27
configure.in: warning: missing AC_CHECK_HEADERS([sys/socket.h]) wanted by: 
src/RemoteSyslogAppender.cpp:26
configure.in: warning: missing AC_CHECK_HEADERS([sys/time.h]) wanted by: 
src/TimeStamp.cpp:15
configure.in: warning: missing AC_CHECK_HEADERS([sys/timeb.h]) wanted by: 
src/TimeStamp.cpp:18
configure.in: warning: missing AC_CHECK_HEADERS([syslog.h]) wanted by: 
include/log4cpp/SyslogAppender.hh:16
configure.in: warning: missing AC_C_CONST wanted by: src/snprintf.c:367
configure.in: warning: missing AC_C_INLINE wanted by: 
src/PortabilityImpl.hh:17
configure.in: warning: missing AC_C_VOLATILE wanted by: 
include/log4cpp/Category.hh:638
configure.in: warning: missing AC_FUNC_ERROR_AT_LINE wanted by: 
src/Category.cpp:347
configure.in: warning: missing AC_FUNC_MALLOC wanted by: src/snprintf.c:428
configure.in: warning: missing AC_FUNC_STRFTIME wanted by: 
src/PatternLayout.cpp:166
configure.in: warning: missing AC_HEADER_STDBOOL wanted by: 
src/Appender.cpp:43
configure.in: warning: missing AC_HEADER_TIME wanted by: src/TimeStamp.cpp:30
configure.in: warning: missing AC_PROG_RANLIB wanted by: config/ltmain.sh:5029
configure.in: warning: missing AC_STRUCT_TM wanted by: 
src/PatternLayout.cpp:151
configure.in: warning: missing AC_TYPE_MODE_T wanted by: 
src/FileAppender.cpp:28
configure.in: warning: missing AC_TYPE_OFF_T wanted by: 
src/RollingFileAppender.cpp:73
configure.in: warning: missing AC_TYPE_SIZE_T wanted by: src/snprintf.c:364

and an autoupdate, followed by an autoreconf -f -i :

/usr/share/aclocal/libmcrypt.m4:17: warning: underquoted definition of 
AM_PATH_LIBMCRYPT
  run info '(automake)Extending aclocal'
  or see http://sources.redhat.com/automake/automake.html#Extending-aclocal
/usr/share/aclocal/glib.m4:8: warning: underquoted definition of AM_PATH_GLIB
Putting files in AC_CONFIG_AUX_DIR, `config'.
/usr/share/aclocal/libmcrypt.m4:17: warning: underquoted definition of 
AM_PATH_LIBMCRYPT
  run info '(automake)Extending aclocal'
  or see http://sources.redhat.com/automake/automake.html#Extending-aclocal
/usr/share/aclocal/glib.m4:8: warning: underquoted definition of AM_PATH_GLIB
configure.in:59: error: possibly undefined macro: AC_C_INT64_T
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.in:60: error: possibly undefined macro: AC_CXX_HAVE_SSTREAM
configure.in:61: error: possibly undefined macro: AC_FUNC_SNPRINTF
configure.in:94: error: possibly undefined macro: AC_CREATE_GENERIC_CONFIG
configure.in:130: error: possibly undefined macro: AC_CREATE_PREFIX_CONFIG_H
autoreconf: /usr/bin/autoconf failed with exit status: 1

who failed, any idea or guideline to follow for an updated build system for 
0.3.4b ?

cheers,

Fathi

Re: [Log4cpp-devel] Questions re log4cpp e-mailing and configuration files

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

Hi,

thanks for your information.

I don't see currently no active developer on log4cpp. But i plan (if i
got any more time) to change the testcases to cppunit. But any developer
who want to start to rework some code is very welcome. I will put your
information about the abilities that have not yet implemented on out
wiki.

regards,

- waffel

On Thu, 2005-12-15 at 10:43 -0800, Daniar, Mohamad wrote:
> Hi :
> 
> --- "Robinson, David N." <Dav...@FM...> wrote:
> 
> > Log4cpp support:
> > 
> > 1. Does log4cpp have the ability to generate e-mails?  In log4j, 
> 
> No.
> Some other abilities (of log4j and/or log4net) that has not been
> implemented :
> - Pick up dynamic configuration change
> - xml format configuration
> - internal log debugging 
> - turn off logging completely
> - buffering
>  
> > 2. The amount of information about how to write configuration files
> > that
> > comes with log4cpp is very limited.  Is more information available
> > about
> > how to write configuration files for log4cpp? 
> 
> Mostly the same with log4j .properties file.
> 
> Other things that come to my concern is that the formatting message
> (PatternLayout) is very slow (at least on Windows platform)
> 
> OOT :
> Is there any active developers who are still developing this code ? 
> 
> 
> 
> Thanks,
> 
> Mohamad Daniar
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Log4cpp-devel mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4cpp-devel

Re: [Log4cpp-devel] Questions re log4cpp e-mailing and configuration files

[Daniar, M. <da...@ya...>]

Hi :

--- "Robinson, David N." <Dav...@FM...> wrote:

> Log4cpp support:
> 
> 1. Does log4cpp have the ability to generate e-mails?  In log4j, 

No.
Some other abilities (of log4j and/or log4net) that has not been
implemented :
- Pick up dynamic configuration change
- xml format configuration
- internal log debugging 
- turn off logging completely
- buffering
 
> 2. The amount of information about how to write configuration files
> that
> comes with log4cpp is very limited.  Is more information available
> about
> how to write configuration files for log4cpp? 

Mostly the same with log4j .properties file.

Other things that come to my concern is that the formatting message
(PatternLayout) is very slow (at least on Windows platform)

OOT :
Is there any active developers who are still developing this code ? 



Thanks,

Mohamad Daniar

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[Log4cpp-devel] Questions re log4cpp e-mailing and configuration files

[Robinson, D. N. <Dav...@FM...>]

Log4cpp support:

1. Does log4cpp have the ability to generate e-mails?  In log4j, I can
configure an appender to send e-mail, in this manner...

    <appender name=3D"SMTPERROR_PROD"
class=3D"org.apache.log4j.net.SMTPAppender">
        <param name=3D"To" value=3D"dav...@fm..." />=20
        <param name=3D"From" value=3D"xy...@ab..." />
        <param name=3D"Subject" value=3D"App xyz ERROR" />
        <param name=3D"SMTPHost" value=3D"mail.def.com" />
        <param name=3D"BufferSize" value=3D"1" />
        <layout class=3D"org.apache.log4j.PatternLayout">
            <param name=3D"ConversionPattern" value=3D"%-6d{ISO8601} =
%-5p
[%t] %c{2} - %m%n"/>
        </layout>
    </appender>

 Can log4cpp be configured in a similar manner?  If not, can it be
programmed in the API?


2. The amount of information about how to write configuration files that
comes with log4cpp is very limited.  Is more information available about
how to write configuration files for log4cpp?=20


Please advise.

Thanks,
	David Robinson (dav...@fm...)

[Log4cpp-devel] get an wiki account

[Bidawi <le....@gm...>]

Hi,
Please, can you create an account for me ?
Thanks,

RE: [Log4cpp-devel] Log4cpp compilation failure on Unix/Solaris.

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

Hi Philippe,

thanks for your report. I can disable this check and commit this to cvs.
After that we can create a new release (windows compile problems fixed
and this check behavior).

Is there is anyone who would help me to port the test to cppunit? It
would be nice if anyone can support me with this task. First of all we
should discuss such porting on our wiki.

Anone there?

Thanks,

- waffel


On Tue, 2005-11-29 at 11:33 +0100, Philippe Haution wrote:
> Hello,
> 
> I am also getting a core dump on the testPattern
> program.
> 
> If you want this test program to run OK, comment out
> these 3 lines in testPattern.cpp :
> test(">%3.5m<%n", layout, cat);
> test(">%.5m<%n", layout, cat);
> 
> ...
> 
> test("%.10m", layout, cat);
> 
> Regards,
> 
> PH
> --- "Robinson, David N." <Dav...@FM...> a
> écrit :
> 
> > Philippe-
> > 
> > Since I could compile with 5.7, I will work with
> > that and skip 5.3 for now.
> > 
> > Can you comment about whether I need to do anything
> > about make check failing with
> > 
> > % 5 cat1:2005-11-23 15:30:40,737 (1132777840 / 5)
> > [ERROR] ndc1 message % (0) 
> > >   message<
> > >message   <
> > FAIL: testPattern
> > 
> > Thanks,
> > 	David
> > 
> > -----Original Message-----
> > From: Philippe Haution
> > [mailto:phi...@ya...] 
> > Sent: Thursday, November 24, 2005 2:29 AM
> > To: Robinson, David N.;
> > log...@li...
> > Subject: RE: [Log4cpp-devel] Log4cpp compilation
> > failure on Unix/Solaris.
> > 
> > 
> > Hello,
> > 
> > Could you install the latest patch (111685-22) for
> > CC
> > 5.3 ?
> > Running "make" works OK for us with this
> > configuration.
> > 
> > Regards,
> > 
> > PH
> > --- "Robinson, David N." <Dav...@FM...>
> > a
> > écrit :
> > 
> > > Philippe-
> > > 
> > > 1. I read the instruction more carefully, and I
> > saw
> > > how to use --prefix to set the installation
> > > directory.
> > > 
> > > 2.  More precisely, when "make check" failed, it
> > > failed with...
> > > % 5 cat1:2005-11-23 15:30:40,737 (1132777840 / 5)
> > > [ERROR] ndc1 message % (0) 
> > > >   message<
> > > >message   <
> > > FAIL: testPattern
> > > 
> > > I still need to know the significance of this and
> > > whether I need to take any action.
> > > 
> > > Thanks,
> > > 	David
> > > 
> > > 
> > > 
> > > -----Original Message-----
> > > From: Robinson, David N. 
> > > Sent: Wednesday, November 23, 2005 2:49 PM
> > > To: 'phi...@mi...'
> > > Subject: RE: [Log4cpp-devel] Log4cpp compilation
> > > failure on Unix/Solaris.
> > > 
> > > 
> > > Philippe-
> > > 
> > > 
> > > 1. I originally tried and fail to run "make" (with
> > > the error indicated) on a box with Sun WorkShop 6
> > > update 2 C++ 5.3 2001/05/15.  I tried again on
> > > another box with Sun C++ 5.7 2005/01/07 and this
> > > successfully completed "make".
> > > 
> > > 
> > > 2. After succeeding with "make", I ran "make
> > check",
> > > and I got this output...
> > > 
> > >
> >
> *************************************************************************************
> > > ====================
> > > 1 of 10 tests failed
> > > ====================
> > > make[2]: *** [check-TESTS] Error 1
> > > make[2]: Leaving directory
> > > `/local2/prod/log4cpp-0.3.5rc3/tests'
> > > make[1]: *** [check-am] Error 2
> > > make[1]: Leaving directory
> > > `/local2/prod/log4cpp-0.3.5rc3/tests'
> > > make: *** [check-recursive] Error 1
> > >
> >
> *************************************************************************************
> > > 
> > > How can I find out exactly what failed and what
> > this
> > > means?  Is there any action that I need to take to
> > > correct this?
> > > 
> > > 
> > > 3. When I run "make install", it tries to install
> > > the libraries to a directory for which I do not
> > have
> > > write access.  How can I reconfigure the code to
> > > install the libraries into a directory which I
> > > specify?
> > > 
> > > 
> > > Thanks,
> > > 	David
> > > 
> > > 
> > > -----Original Message-----
> > > From: Philippe Haution
> > > [mailto:phi...@ya...] 
> > > Sent: Wednesday, November 23, 2005 9:47 AM
> > > To: Robinson, David N.;
> > > phi...@mi...
> > > Subject: RE: [Log4cpp-devel] Log4cpp compilation
> > > failure on Unix/Solaris.
> > > 
> > > 
> > > I was talking about your compiler's version.
> > > 
> > > PH
> > > --- "Robinson, David N."
> > <Dav...@FM...>
> > > a
> > > écrit :
> > > 
> > > > Philippe-
> > > > 
> > > > The tar file that I used is
> > log4cpp-0.3.5rc3.tar.
> > > > 
> > > > Thanks,
> > > > 	David
> > > > 
> > > > -----Original Message-----
> > > > From: Philippe Haution
> > > > [mailto:phi...@ya...] 
> > > > Sent: Wednesday, November 23, 2005 7:06 AM
> > > > To: Robinson, David N.;
> > > > log...@li...
> > > > Subject: RE: [Log4cpp-devel] Log4cpp compilation
> > > > failure on Unix/Solaris.
> > > > 
> > > > 
> > > > Hello,
> > > > 
> > > > Could you be more precise about the release and
> > > > patch
> > > > number your are using ?
> > > > 
> > > > My first guess is that Sun CC shouldn't produce
> > an
> > > > error message since it is legal C++ to have a
> > > > virtual
> > > > method in a derived class be more restrictive
> > than
> > > > the
> > > > base method in its exception specification.
> > > > 
> > > > However, it would perhaps be a good idea to
> > > reassess
> > > > the opportunity to use exception specifications
> > in
> > > > log4cpp now that the C++ community knows they
> > > should
> > > > be avoided.
> > > > 
> > > > Regards,
> > > > 
> > > > PH
> > > > 
> > > > --- "Robinson, David N."
> > > <Dav...@FM...>
> > > > a
> > > > écrit :
> > > > 
> > > > > Log4cpp support:
> > > > > 
> > > > > When I try to install log4cpp on Unix/Solaris,
> > I
> > > > get
> > > > > the following error
> > > > > after I run the make command:
> > > > > 
> > > > > source='FixedContextCategory.cpp'
> > > > > object='FixedContextCategory.lo'
> > > > > libtool=yes \
> > > > > DEPDIR=.deps depmode=none /bin/bash
> > > > > ../config/depcomp \
> > 
> === message truncated ===
> 
> 
> 
> 	
> 
> 	
> 		
> ___________________________________________________________________________ 
> Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
> Téléchargez cette version sur http://fr.messenger.yahoo.com
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Log4cpp-devel mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4cpp-devel

RE: [Log4cpp-devel] Log4cpp compilation failure on Unix/Solaris.

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

Hello,

I am also getting a core dump on the testPattern
program.

If you want this test program to run OK, comment out
these 3 lines in testPattern.cpp :
test(">%3.5m<%n", layout, cat);
test(">%.5m<%n", layout, cat);

...

test("%.10m", layout, cat);

Regards,

PH
--- "Robinson, David N." <Dav...@FM...> a
écrit :

> Philippe-
> 
> Since I could compile with 5.7, I will work with
> that and skip 5.3 for now.
> 
> Can you comment about whether I need to do anything
> about make check failing with
> 
> % 5 cat1:2005-11-23 15:30:40,737 (1132777840 / 5)
> [ERROR] ndc1 message % (0) 
> >   message<
> >message   <
> FAIL: testPattern
> 
> Thanks,
> 	David
> 
> -----Original Message-----
> From: Philippe Haution
> [mailto:phi...@ya...] 
> Sent: Thursday, November 24, 2005 2:29 AM
> To: Robinson, David N.;
> log...@li...
> Subject: RE: [Log4cpp-devel] Log4cpp compilation
> failure on Unix/Solaris.
> 
> 
> Hello,
> 
> Could you install the latest patch (111685-22) for
> CC
> 5.3 ?
> Running "make" works OK for us with this
> configuration.
> 
> Regards,
> 
> PH
> --- "Robinson, David N." <Dav...@FM...>
> a
> écrit :
> 
> > Philippe-
> > 
> > 1. I read the instruction more carefully, and I
> saw
> > how to use --prefix to set the installation
> > directory.
> > 
> > 2.  More precisely, when "make check" failed, it
> > failed with...
> > % 5 cat1:2005-11-23 15:30:40,737 (1132777840 / 5)
> > [ERROR] ndc1 message % (0) 
> > >   message<
> > >message   <
> > FAIL: testPattern
> > 
> > I still need to know the significance of this and
> > whether I need to take any action.
> > 
> > Thanks,
> > 	David
> > 
> > 
> > 
> > -----Original Message-----
> > From: Robinson, David N. 
> > Sent: Wednesday, November 23, 2005 2:49 PM
> > To: 'phi...@mi...'
> > Subject: RE: [Log4cpp-devel] Log4cpp compilation
> > failure on Unix/Solaris.
> > 
> > 
> > Philippe-
> > 
> > 
> > 1. I originally tried and fail to run "make" (with
> > the error indicated) on a box with Sun WorkShop 6
> > update 2 C++ 5.3 2001/05/15.  I tried again on
> > another box with Sun C++ 5.7 2005/01/07 and this
> > successfully completed "make".
> > 
> > 
> > 2. After succeeding with "make", I ran "make
> check",
> > and I got this output...
> > 
> >
>
*************************************************************************************
> > ====================
> > 1 of 10 tests failed
> > ====================
> > make[2]: *** [check-TESTS] Error 1
> > make[2]: Leaving directory
> > `/local2/prod/log4cpp-0.3.5rc3/tests'
> > make[1]: *** [check-am] Error 2
> > make[1]: Leaving directory
> > `/local2/prod/log4cpp-0.3.5rc3/tests'
> > make: *** [check-recursive] Error 1
> >
>
*************************************************************************************
> > 
> > How can I find out exactly what failed and what
> this
> > means?  Is there any action that I need to take to
> > correct this?
> > 
> > 
> > 3. When I run "make install", it tries to install
> > the libraries to a directory for which I do not
> have
> > write access.  How can I reconfigure the code to
> > install the libraries into a directory which I
> > specify?
> > 
> > 
> > Thanks,
> > 	David
> > 
> > 
> > -----Original Message-----
> > From: Philippe Haution
> > [mailto:phi...@ya...] 
> > Sent: Wednesday, November 23, 2005 9:47 AM
> > To: Robinson, David N.;
> > phi...@mi...
> > Subject: RE: [Log4cpp-devel] Log4cpp compilation
> > failure on Unix/Solaris.
> > 
> > 
> > I was talking about your compiler's version.
> > 
> > PH
> > --- "Robinson, David N."
> <Dav...@FM...>
> > a
> > écrit :
> > 
> > > Philippe-
> > > 
> > > The tar file that I used is
> log4cpp-0.3.5rc3.tar.
> > > 
> > > Thanks,
> > > 	David
> > > 
> > > -----Original Message-----
> > > From: Philippe Haution
> > > [mailto:phi...@ya...] 
> > > Sent: Wednesday, November 23, 2005 7:06 AM
> > > To: Robinson, David N.;
> > > log...@li...
> > > Subject: RE: [Log4cpp-devel] Log4cpp compilation
> > > failure on Unix/Solaris.
> > > 
> > > 
> > > Hello,
> > > 
> > > Could you be more precise about the release and
> > > patch
> > > number your are using ?
> > > 
> > > My first guess is that Sun CC shouldn't produce
> an
> > > error message since it is legal C++ to have a
> > > virtual
> > > method in a derived class be more restrictive
> than
> > > the
> > > base method in its exception specification.
> > > 
> > > However, it would perhaps be a good idea to
> > reassess
> > > the opportunity to use exception specifications
> in
> > > log4cpp now that the C++ community knows they
> > should
> > > be avoided.
> > > 
> > > Regards,
> > > 
> > > PH
> > > 
> > > --- "Robinson, David N."
> > <Dav...@FM...>
> > > a
> > > écrit :
> > > 
> > > > Log4cpp support:
> > > > 
> > > > When I try to install log4cpp on Unix/Solaris,
> I
> > > get
> > > > the following error
> > > > after I run the make command:
> > > > 
> > > > source='FixedContextCategory.cpp'
> > > > object='FixedContextCategory.lo'
> > > > libtool=yes \
> > > > DEPDIR=.deps depmode=none /bin/bash
> > > > ../config/depcomp \
> 
=== message truncated ===



	

	
		
___________________________________________________________________________ 
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
Téléchargez cette version sur http://fr.messenger.yahoo.com

RE: [Log4cpp-devel] Log4cpp compilation failure on Unix/Solaris.

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

Hello,

Could you install the latest patch (111685-22) for CC
5.3 ?
Running "make" works OK for us with this
configuration.

Regards,

PH
--- "Robinson, David N." <Dav...@FM...> a
écrit :

> Philippe-
> 
> 1. I read the instruction more carefully, and I saw
> how to use --prefix to set the installation
> directory.
> 
> 2.  More precisely, when "make check" failed, it
> failed with...
> % 5 cat1:2005-11-23 15:30:40,737 (1132777840 / 5)
> [ERROR] ndc1 message % (0) 
> >   message<
> >message   <
> FAIL: testPattern
> 
> I still need to know the significance of this and
> whether I need to take any action.
> 
> Thanks,
> 	David
> 
> 
> 
> -----Original Message-----
> From: Robinson, David N. 
> Sent: Wednesday, November 23, 2005 2:49 PM
> To: 'phi...@mi...'
> Subject: RE: [Log4cpp-devel] Log4cpp compilation
> failure on Unix/Solaris.
> 
> 
> Philippe-
> 
> 
> 1. I originally tried and fail to run "make" (with
> the error indicated) on a box with Sun WorkShop 6
> update 2 C++ 5.3 2001/05/15.  I tried again on
> another box with Sun C++ 5.7 2005/01/07 and this
> successfully completed "make".
> 
> 
> 2. After succeeding with "make", I ran "make check",
> and I got this output...
> 
>
*************************************************************************************
> ====================
> 1 of 10 tests failed
> ====================
> make[2]: *** [check-TESTS] Error 1
> make[2]: Leaving directory
> `/local2/prod/log4cpp-0.3.5rc3/tests'
> make[1]: *** [check-am] Error 2
> make[1]: Leaving directory
> `/local2/prod/log4cpp-0.3.5rc3/tests'
> make: *** [check-recursive] Error 1
>
*************************************************************************************
> 
> How can I find out exactly what failed and what this
> means?  Is there any action that I need to take to
> correct this?
> 
> 
> 3. When I run "make install", it tries to install
> the libraries to a directory for which I do not have
> write access.  How can I reconfigure the code to
> install the libraries into a directory which I
> specify?
> 
> 
> Thanks,
> 	David
> 
> 
> -----Original Message-----
> From: Philippe Haution
> [mailto:phi...@ya...] 
> Sent: Wednesday, November 23, 2005 9:47 AM
> To: Robinson, David N.;
> phi...@mi...
> Subject: RE: [Log4cpp-devel] Log4cpp compilation
> failure on Unix/Solaris.
> 
> 
> I was talking about your compiler's version.
> 
> PH
> --- "Robinson, David N." <Dav...@FM...>
> a
> écrit :
> 
> > Philippe-
> > 
> > The tar file that I used is log4cpp-0.3.5rc3.tar.
> > 
> > Thanks,
> > 	David
> > 
> > -----Original Message-----
> > From: Philippe Haution
> > [mailto:phi...@ya...] 
> > Sent: Wednesday, November 23, 2005 7:06 AM
> > To: Robinson, David N.;
> > log...@li...
> > Subject: RE: [Log4cpp-devel] Log4cpp compilation
> > failure on Unix/Solaris.
> > 
> > 
> > Hello,
> > 
> > Could you be more precise about the release and
> > patch
> > number your are using ?
> > 
> > My first guess is that Sun CC shouldn't produce an
> > error message since it is legal C++ to have a
> > virtual
> > method in a derived class be more restrictive than
> > the
> > base method in its exception specification.
> > 
> > However, it would perhaps be a good idea to
> reassess
> > the opportunity to use exception specifications in
> > log4cpp now that the C++ community knows they
> should
> > be avoided.
> > 
> > Regards,
> > 
> > PH
> > 
> > --- "Robinson, David N."
> <Dav...@FM...>
> > a
> > écrit :
> > 
> > > Log4cpp support:
> > > 
> > > When I try to install log4cpp on Unix/Solaris, I
> > get
> > > the following error
> > > after I run the make command:
> > > 
> > > source='FixedContextCategory.cpp'
> > > object='FixedContextCategory.lo'
> > > libtool=yes \
> > > DEPDIR=.deps depmode=none /bin/bash
> > > ../config/depcomp \
> > > /bin/bash ../libtool --tag=CXX --mode=compile CC
> > > -DHAVE_CONFIG_H -I. -I.
> > > -I../include -I../include    -g -c -o
> > > FixedContextCategory.lo
> > > FixedContextCategory.cpp
> > >  CC -DHAVE_CONFIG_H -I. -I. -I../include
> > > -I../include -g -c
> > > FixedContextCategory.cpp  -KPIC -DPIC -o
> > > .libs/FixedContextCategory.o
> > > "../include/log4cpp/FixedContextCategory.hh",
> line
> > > 80: Error: Function
> > >
> >
>
log4cpp::FixedContextCategory::addAppender(log4cpp::Appender*)
> > > can throw
> > > only the exceptions thrown by the function
> > >
> log4cpp::Category::addAppender(log4cpp::Appender*)
> > > it overrides.
> > > "../include/log4cpp/FixedContextCategory.hh",
> line
> > > 171: Warning:
> > > log4cpp::FixedContextCategory::ownsAppender
> hides
> > > the virtual function
> > >
> >
> log4cpp::Category::ownsAppender(log4cpp::Appender*,
> > > __rwstd::__rb_tree<log4cpp::Appender*,
> > > std::pair<log4cpp::Appender*const, bool>,
> > >
> >
>
__rwstd::__select1st<std::pair<log4cpp::Appender*const,
> > > bool>,
> > > log4cpp::Appender*>,
> > std::less<log4cpp::Appender*>,
> > >
> std::allocator<std::pair<log4cpp::Appender*const,
> > > bool>>>::iterator&).
> > > 1 Error(s) and 1 Warning(s) detected.
> > > make[1]: *** [FixedContextCategory.lo] Error 1
> > > make[1]: Leaving directory
> > > `/local2/prod/log4cpp-0.3.5rc3/src'
> > > make: *** [all-recursive] Error 1
> > > 
> > > Note that I set
> > > 	CC=CC CXX=CC LD="CC -KPIC" ./configure
> > > --disable-static
> > > per the INSTALL instructions.
> > > 
> > > Please advise.
> > > 
> > > Thanks,
> 
=== message truncated ===



	

	
		
___________________________________________________________________________ 
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
Téléchargez cette version sur http://fr.messenger.yahoo.com

RE: [Log4cpp-devel] Log4cpp compilation failure on Unix/Solaris.

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

Hello,

Could you be more precise about the release and patch
number your are using ?

My first guess is that Sun CC shouldn't produce an
error message since it is legal C++ to have a virtual
method in a derived class be more restrictive than the
base method in its exception specification.

However, it would perhaps be a good idea to reassess
the opportunity to use exception specifications in
log4cpp now that the C++ community knows they should
be avoided.

Regards,

PH

--- "Robinson, David N." <Dav...@FM...> a
écrit :

> Log4cpp support:
> 
> When I try to install log4cpp on Unix/Solaris, I get
> the following error
> after I run the make command:
> 
> source='FixedContextCategory.cpp'
> object='FixedContextCategory.lo'
> libtool=yes \
> DEPDIR=.deps depmode=none /bin/bash
> ../config/depcomp \
> /bin/bash ../libtool --tag=CXX --mode=compile CC
> -DHAVE_CONFIG_H -I. -I.
> -I../include -I../include    -g -c -o
> FixedContextCategory.lo
> FixedContextCategory.cpp
>  CC -DHAVE_CONFIG_H -I. -I. -I../include
> -I../include -g -c
> FixedContextCategory.cpp  -KPIC -DPIC -o
> .libs/FixedContextCategory.o
> "../include/log4cpp/FixedContextCategory.hh", line
> 80: Error: Function
>
log4cpp::FixedContextCategory::addAppender(log4cpp::Appender*)
> can throw
> only the exceptions thrown by the function
> log4cpp::Category::addAppender(log4cpp::Appender*)
> it overrides.
> "../include/log4cpp/FixedContextCategory.hh", line
> 171: Warning:
> log4cpp::FixedContextCategory::ownsAppender hides
> the virtual function
> log4cpp::Category::ownsAppender(log4cpp::Appender*,
> __rwstd::__rb_tree<log4cpp::Appender*,
> std::pair<log4cpp::Appender*const, bool>,
>
__rwstd::__select1st<std::pair<log4cpp::Appender*const,
> bool>,
> log4cpp::Appender*>, std::less<log4cpp::Appender*>,
> std::allocator<std::pair<log4cpp::Appender*const,
> bool>>>::iterator&).
> 1 Error(s) and 1 Warning(s) detected.
> make[1]: *** [FixedContextCategory.lo] Error 1
> make[1]: Leaving directory
> `/local2/prod/log4cpp-0.3.5rc3/src'
> make: *** [all-recursive] Error 1
> 
> Note that I set
> 	CC=CC CXX=CC LD="CC -KPIC" ./configure
> --disable-static
> per the INSTALL instructions.
> 
> Please advise.
> 
> Thanks,
> 	David Robinson (dav...@fm...)
> 
> 



	

	
		
___________________________________________________________________________ 
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
Téléchargez cette version sur http://fr.messenger.yahoo.com

[Log4cpp-devel] Log4cpp compilation failure on Unix/Solaris.

[Robinson, D. N. <Dav...@FM...>]

Log4cpp support:

When I try to install log4cpp on Unix/Solaris, I get the following error
after I run the make command:

source=3D'FixedContextCategory.cpp' object=3D'FixedContextCategory.lo'
libtool=3Dyes \
DEPDIR=3D.deps depmode=3Dnone /bin/bash ../config/depcomp \
/bin/bash ../libtool --tag=3DCXX --mode=3Dcompile CC -DHAVE_CONFIG_H -I. =
-I.
-I../include -I../include    -g -c -o FixedContextCategory.lo
FixedContextCategory.cpp
 CC -DHAVE_CONFIG_H -I. -I. -I../include -I../include -g -c
FixedContextCategory.cpp  -KPIC -DPIC -o .libs/FixedContextCategory.o
"../include/log4cpp/FixedContextCategory.hh", line 80: Error: Function
log4cpp::FixedContextCategory::addAppender(log4cpp::Appender*) can throw
only the exceptions thrown by the function
log4cpp::Category::addAppender(log4cpp::Appender*) it overrides.
"../include/log4cpp/FixedContextCategory.hh", line 171: Warning:
log4cpp::FixedContextCategory::ownsAppender hides the virtual function
log4cpp::Category::ownsAppender(log4cpp::Appender*,
__rwstd::__rb_tree<log4cpp::Appender*,
std::pair<log4cpp::Appender*const, bool>,
__rwstd::__select1st<std::pair<log4cpp::Appender*const, bool>,
log4cpp::Appender*>, std::less<log4cpp::Appender*>,
std::allocator<std::pair<log4cpp::Appender*const, bool>>>::iterator&).
1 Error(s) and 1 Warning(s) detected.
make[1]: *** [FixedContextCategory.lo] Error 1
make[1]: Leaving directory `/local2/prod/log4cpp-0.3.5rc3/src'
make: *** [all-recursive] Error 1

Note that I set
	CC=3DCC CXX=3DCC LD=3D"CC -KPIC" ./configure --disable-static
per the INSTALL instructions.

Please advise.

Thanks,
	David Robinson (dav...@fm...)

Re: [Log4cpp-devel] forgotten AportAppender msvc6

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

Hi,

thank you Amanjit! I have committed the changes to cvs ... hope it works
now.

Regards,

waffel

On Wed, 2005-10-12 at 10:40 +0200, Amanjit Gill wrote:
> Thomas Wabner wrote:
> 
> > Amanjit: Can you please verify this short? If all thinks then ok I will
> > create the new release :-)
> 
> Hi, I didn't have the time to do sooner.
> 
> - MSVC6 is no problem
> - With VC7 vcproj) we need the following changes (tested with Visual 
> Studio 8 Beta 2): In log4cpp.proj:
> 
> search for this xml
> -old-------------------------------------
> 	<Tool
> 	  Name="VCCLCompilerTool"
> 	  Optimization="0"
> --------------------------------------
> 
> -new-------------------------------------
> 	<Tool
> 	  Name="VCCLCompilerTool"
>            AdditionalIncludeDirectories="../../include"
> 	  Optimization="0"
> --------------------------------------
> - we have a problem with linefeeds (CR/Vs CR/LF vs LF) in Priority.h and 
> Priority.cpp (I think it is somehow mixed?). I do not think my CVS 
> client messed this up. This has to be checked and changed back to unix 
> LF imho
> 
> Greetings
> 
> _________________________
> Amanjit Gill
> Software Developer
> neofonie
> Technologieentwicklung und
> Informationsmanagement GmBH
> 
> Robert-Koch-Platz 4
> 10115 Berlin
> am...@ne...
> 
> DISCLAIMER
> Any opinion expressed in this post is the personal opinion of Amanjit 
> Gill and can in no way be constructed as an official statement by his 
> employer

Re: [Log4cpp-devel] forgotten AportAppender msvc6

[Amanjit G. <ama...@gm...>]

Thomas Wabner wrote:

> Amanjit: Can you please verify this short? If all thinks then ok I will
> create the new release :-)

Hi, I didn't have the time to do sooner.

- MSVC6 is no problem
- With VC7 vcproj) we need the following changes (tested with Visual 
Studio 8 Beta 2): In log4cpp.proj:

search for this xml
-old-------------------------------------
	<Tool
	  Name="VCCLCompilerTool"
	  Optimization="0"
--------------------------------------

-new-------------------------------------
	<Tool
	  Name="VCCLCompilerTool"
           AdditionalIncludeDirectories="../../include"
	  Optimization="0"
--------------------------------------
- we have a problem with linefeeds (CR/Vs CR/LF vs LF) in Priority.h and 
Priority.cpp (I think it is somehow mixed?). I do not think my CVS 
client messed this up. This has to be checked and changed back to unix 
LF imho

Greetings

_________________________
Amanjit Gill
Software Developer
neofonie
Technologieentwicklung und
Informationsmanagement GmBH

Robert-Koch-Platz 4
10115 Berlin
am...@ne...

DISCLAIMER
Any opinion expressed in this post is the personal opinion of Amanjit 
Gill and can in no way be constructed as an official statement by his 
employer

Re: [Log4cpp-devel] forgotten AportAppender msvc6

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

Hi,

I have added the entry and commited to cvs. 

Amanjit: Can you please verify this short? If all thinks then ok I will
create the new release :-)

Thanks,

- waffel

On Thu, 2005-10-06 at 00:38 +0200, Amanjit Gill wrote:
> Thomas Wabner wrote:
> > But I hope all thinks are working now. Can you please verify this, thus
> > I can create a new bugfix release?
> > 
> > Many thanks again for your support!
> 
> Thank _you_ for your support. I am sorry the patch failed but it wasn't 
> a complete waste of time. All normal libs (static and dlls) now build 
> (stlport boost doesnt)
> 
> all we need is the inclusion of the AbortAppender.cpp file in the 
> log4cpp.dsp file (corresponds to the Makefile.am entry)
> 
> in file log4cpp.dsp
> ----------------cut------------------
> SOURCE=..\..\src\AbortAppender.cpp
> # End Source File
> # Begin Source File
> ----------------cut------------------
> 
> it should be behind the line '# Begin Group "Source Files"' at ~ line 
> 88, where all other source files lie
> 
> Hope thats it !!!
> Greetings
> 
> _________________________
> Amanjit Gill
> Software Developer
> neofonie
> Technologieentwicklung und
> Informationsmanagement GmBH
> 
> Robert-Koch-Platz 4
> 10115 Berlin
> am...@ne...
> 
> DISCLAIMER
> Any opinion expressed in this post is the personal opinion of Amanjit 
> Gill and can in no way be constructed as an official statement by his 
> employer

[Fwd: Re: [Log4cpp-devel] (no subject)]

[Amanjit G. <ama...@gm...>]

FYI

Greetings

_________________________
Amanjit Gill
Software Developer
neofonie
Technologieentwicklung und
Informationsmanagement GmBH

Robert-Koch-Platz 4
10115 Berlin
am...@ne...

DISCLAIMER
Any opinion expressed in this post is the personal opinion of Amanjit 
Gill and can in no way be constructed as an official statement by his 
employer

Re: [Log4cpp-devel] (no subject)

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

Hi Amanjit,

thanks for your patch. I have tried to apply it but got some rejections.
I have converted for myself the files from dos2unix and commited them to
cvs. Here comes the list of rejected files:

atching file include/log4cpp/Priority.hh
patching file msvc6/msvc6.dsw
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file msvc6/msvc6.dsw.rej
patching file msvc6/log4cpp/log4cpp.dsp
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file
msvc6/log4cpp/log4cpp.dsp.rej
patching file msvc6/log4cppDLL/log4cppDLL.dsp
Reversed (or previously applied) patch detected!  Assume -R? [n] y
patching file msvc6/testCategory/testCategory.dsp
Reversed (or previously applied) patch detected!  Assume -R? [n] y
patching file msvc6/testDLL/testDLL.dsp
Reversed (or previously applied) patch detected!  Assume -R? [n] y
patching file msvc6/testMain/testMain.dsp
Reversed (or previously applied) patch detected!  Assume -R? [n] y
patching file msvc6/testNDC/testNDC.dsp
Reversed (or previously applied) patch detected!  Assume -R? [n] y
patching file msvc6/testNTEventLog/testNTEventLog.dsp
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file
msvc6/testNTEventLog/testNTEventLog.dsp.rej
patching file msvc6/testPattern/testPattern.dsp
Reversed (or previously applied) patch detected!  Assume -R? [n] y
patching file msvc6/testPropConfig/testPropConfig.dsp
Hunk #1 FAILED at 49.
Hunk #2 FAILED at 73.
2 out of 2 hunks FAILED -- saving rejects to file
msvc6/testPropConfig/testPropConfig.dsp.rej
patching file src/Priority.cpp


But I hope all thinks are working now. Can you please verify this, thus
I can create a new bugfix release?

Many thanks again for your support!

- waffel

Re: [Log4cpp-devel] (no subject)

[Amanjit G. <ama...@gm...>]

Thomas Wabner wrote:


> now I have commited the patches from Amanjit. Hopfully don't forget something! Can anyone test it (check it out from cvs)? If I got a positiv test feedback, I will create a new beta release for all mcvc6 freaks :-)

Hi Thomas I sent you a patch with some small fixes via personal mail.

Hopefully everything works now.

Greetings

_________________________
Amanjit Gill
Software Developer
neofonie
Technologieentwicklung und
Informationsmanagement GmBH

Robert-Koch-Platz 4
10115 Berlin
am...@ne...

DISCLAIMER
Any opinion expressed in this post is the personal opinion of Amanjit
Gill and can in no way be constructed as an official statement by his
employer

Re: [Log4cpp-devel] (no subject)

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

Hi,

now I have commited the patches from Amanjit. Hopfully don't forget someth=
ing! Can anyone test it (check it out from cvs)? If I got a positiv test f=
eedback, I will create a new beta release for all mcvc6 freaks :-)

Regards,

waffel

> =C8=CE=BE=AD=CE=B3 wrote:
>=20
> > Hi,
> > =20 I am a new user of log4cpp. I download the package from the source=
forge.
> > The version is 0.3.5rc3. I uncompressed it in windows 2000. Then I com=
pile=20
> > it using MSVC6. When I open the workspace named msvc6.dsw using MSVC6,=
 it
> > tell me browse for log4cppDLL_stlport_boost.dsp and etc.. I cann't fin=
d such project
> > in the package. I don't know how to get such projects.
> > Thank you very much!
> >=20
>=20
> Hi, I have to go to work now, I have sent you a new msvc6 folder as a pm=

> (zip.. contains no executables), which will do the job.
>=20
> If you do not use STLPort, the testPattern test will not work due to
> limitations of VC6 (dinkumware) STL. (String too long :)). Use STLport
> in that case (5.0CVS). In that case, ensure
> LOG4CPP_MISSING_INT64_OSTREAM_OP is not set in config-win32.h, because
> STLport provides this operator (will generate compile-time-ambiguity)
>=20
> Greetings,
> _________________________
> Amanjit Gill
> Software Developer
> neofonie
> Technologieentwicklung und
> Informationsmanagement GmBH
>=20
> Robert-Koch-Platz 4
> 10115 Berlin
> am...@ne...
>=20
> DISCLAIMER
> Any opinion expressed in this post is the personal opinion of Amanjit
> Gill and can in no way be constructed as an official statement by his
> employer
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server. Down=
load
> it for free - -and be entered to win a 42" plasma tv or your very own
> Sony(tm)PSP. =20Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> Log4cpp-devel mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4cpp-devel

Re: [Log4cpp-devel] (no subject)

[Amanjit G. <ama...@gm...>]

任经纬 wrote:

> Hi,
>   I am a new user of log4cpp. I download the package from the sourceforge.
> The version is 0.3.5rc3. I uncompressed it in windows 2000. Then I compile 
> it using MSVC6. When I open the workspace named msvc6.dsw using MSVC6, it
> tell me browse for log4cppDLL_stlport_boost.dsp and etc.. I cann't find such project
> in the package. I don't know how to get such projects.
> Thank you very much!
> 

Hi, I have to go to work now, I have sent you a new msvc6 folder as a pm
(zip.. contains no executables), which will do the job.

If you do not use STLPort, the testPattern test will not work due to
limitations of VC6 (dinkumware) STL. (String too long :)). Use STLport
in that case (5.0CVS). In that case, ensure
LOG4CPP_MISSING_INT64_OSTREAM_OP is not set in config-win32.h, because
STLport provides this operator (will generate compile-time-ambiguity)

Greetings,
_________________________
Amanjit Gill
Software Developer
neofonie
Technologieentwicklung und
Informationsmanagement GmBH

Robert-Koch-Platz 4
10115 Berlin
am...@ne...

DISCLAIMER
Any opinion expressed in this post is the personal opinion of Amanjit
Gill and can in no way be constructed as an official statement by his
employer

Re: [Log4cpp-devel] (no subject)

[Amanjit G. <ama...@gm...>]

Fathi Boudra wrote:

> i tried to build it on windows 2000 - MSVC6. All 0.3.5rc builds are broken.
> the 0.3.4b version builds fine. Like said before, it seems that there's not 
> the boost related projects in the source archive provided.

Regarding MSVC6

Hi there, I am actually just fixing this right now, and will provide a 
patch if acceptable for the mailing list.

If you want to go on manually, its not that hard !

1. ignore the missing .dsp files. Kick out the TestDLL.dsp because the
    test does not exist ist /tests
2. Priority.hh:
    static const int MESSAGE_SIZE = 8;
    must move into the cpp file (for msvc6)
    --> const int log4cpp::Priority::MESSAGE_SIZE = 8;
    (in the namespace, of course).
3. the test files must link statically with the appropriate release and 
debug versions
4. with STLPort you need some changes aswell..

Greetings
_________________________
Amanjit Gill
Software Developer
neofonie
Technologieentwicklung und
Informationsmanagement GmBH

Robert-Koch-Platz 4
10115 Berlin
am...@ne...

DISCLAIMER
Any opinion expressed in this post is the personal opinion of Amanjit 
Gill and can in no way be constructed as an official statement by his 
employer

Re: [Log4cpp-devel] (no subject)

[stensil <st...@li...>]

FB> > >   I am a new user of log4cpp. I download the package from the
FB> > > sourceforge. The version is 0.3.5rc3. I uncompressed it in windows 2000.
FB> > > Then I compile it using MSVC6. When I open the workspace named msvc6.dsw
FB> > > using MSVC6, it tell me browse for log4cppDLL_stlport_boost.dsp and etc..
FB> > > I cann't find such project in the package. I don't know how to get such
FB> > > projects.
FB> 
FB> > is there is anyone in this list which uses a windows box and have
FB> > compiled log4cpp with MSVC6? Please help us guys to get it working again
FB> > also under windows. For myself I have no windows box :-)
FB> > > Thank you very much!
FB> 
FB> i tried to build it on windows 2000 - MSVC6. All 0.3.5rc builds are broken.
FB> the 0.3.4b version builds fine. Like said before, it seems that there's not 
FB> the boost related projects in the source archive provided.

I successfully compiled it on VC.NET2003 (after some corrections).

FB> Another error (under linux), typo in the file include/log4cpp/Manipulator.hh 
FB> line 29 there's an extra "; "

Re: [Log4cpp-devel] (no subject)

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

> >   I am a new user of log4cpp. I download the package from the
> > sourceforge. The version is 0.3.5rc3. I uncompressed it in windows 2000.
> > Then I compile it using MSVC6. When I open the workspace named msvc6.dsw
> > using MSVC6, it tell me browse for log4cppDLL_stlport_boost.dsp and etc..
> > I cann't find such project in the package. I don't know how to get such
> > projects.

> is there is anyone in this list which uses a windows box and have
> compiled log4cpp with MSVC6? Please help us guys to get it working again
> also under windows. For myself I have no windows box :-)
> > Thank you very much!

i tried to build it on windows 2000 - MSVC6. All 0.3.5rc builds are broken.
the 0.3.4b version builds fine. Like said before, it seems that there's not 
the boost related projects in the source archive provided.

Another error (under linux), typo in the file include/log4cpp/Manipulator.hh 
line 29 there's an extra "; "

cheers,

Fathi