log4cplus-devel — Mailing list for log4cplus developers

[Log4cplus-devel] log4cplus 2.1.1 released

[Václav H. <vha...@gm...>]

I have released log4cplus 2.1.1. This is a maintenance release with one 
new feature.


    - Add missing source files to MSVC project files.

    - Resolve environment variables in include directive in 
configuration file. (Martin Engelmann)


-- 
VH

[Log4cplus-devel] log4cplus 2.1.0 released

[Václav H. <vha...@gm...>]

I have released log4cplus 2.1.0.

This release breaks ABI with 2.0.x. It is source compatible.

   - Throw exception on nonexistent properties file,
     if requested by `fThrow` flag.

   - Generate pkgconfig file with CMake.

   - Add locale support to `ConsoleAppender`. (Choy Kho Yee)

   - Initialize thread pool for async logging on demand.

   - `SysLogAppender`: Allow non-FQDN hostname
     in syslog messages.

   - Update Catch2 to v2.13.9.

-- 
VH

Re: [Log4cplus-devel] Confirm logger that doesn't exist

[Václav H. <vha...@gm...>]

On 06. 02. 23 14:42, Richard, Charles via Log4cplus-devel wrote:
> Hi,
> 
> We are using the log4cplus library for one of our projects and I would 
> like to implement functionality that informs a user if they have 
> requested changes to a logger that doesn’t exist in our log file.

This is not possible. The logger can appear any time in the future or 
not at all. You can instantiate and use loggers that are not
defined in the configuration.

> 
> To do so, I would need some way to either be able to make a call to 
> log4cplus and get some kind of return value of whether the logger exists 
> or not or a way to iterate through the loggers.
> 
> I tried looking this up in the api documentation but the current link to 
> the api documentation is broken 
> (https://log4cplus.sourceforge.io/docs/api/2.0.x/ 
> <https://log4cplus.sourceforge.io/docs/api/2.0.x/>).
> 
> Any help would be greatly appreciated!
> 
> Thanks,
> 
> Charles
> 
> 
> Internal Use - Confidential

Nope.



-- 
VH

[Log4cplus-devel] Confirm logger that doesn't exist

[Richard, C. <Cha...@de...>]

Hi,

We are using the log4cplus library for one of our projects and I would like to implement functionality that informs a user if they have requested changes to a logger that doesn't exist in our log file.

To do so, I would need some way to either be able to make a call to log4cplus and get some kind of return value of whether the logger exists or not or a way to iterate through the loggers.

I tried looking this up in the api documentation but the current link to the api documentation is broken (https://log4cplus.sourceforge.io/docs/api/2.0.x/).

Any help would be greatly appreciated!

Thanks,
Charles


Internal Use - Confidential

[Log4cplus-devel] log4cplus 2.0.8 released

[Václav H. <vha...@gm...>]

I have released log4cplus 2.0.8. It is a maintenance release.

  - Add CMake alias libraries. GitHub issue #511.

  - Add an option to disable tests to `configure` script. (Fabrice Fontaine)

  - Fix C++11 compatibility: C++11 does not have `basic_string_view`.

  - Look for Android's `log` library. GitHub issue #543.

  - Fix handling of `,aux` extension for `FileAppender`. GitHub issue
#534. (Pieter du Preez)

  - `filename` should not be empty for `TimeBasedRollingFileAppender`.
GitHub issue #517. (Fox Chen)


-- 
VH

[Log4cplus-devel] log4cplus 2.0.7 released

[Václav H. <vha...@gm...>]

I have released log4cplus 2.0.7. It is a maintenance release.

  - Fix compilation with C++20 compiler, use std::invoke_result.

  - TimeBasedRollingFileAppender: Clear files before `MaxHistory` when
`CleanHistoryOnStart=false`.

  - Update embedded Catch2 to version v2.13.7 to compilation with
current Glibc. GitHub issue #519.


-- 
VH

[Log4cplus-devel] log4cplus 2.0.6 released

[Václav H. <vha...@gm...>]

I have released log4cplus 2.0.6. It is maintenance release. The main
change is the ability to disable internal thread pool which causes
issues when unloading DLLs.

  - Fixes to internal thread pool.

  - Internal thread pool can now be disabled during compilation. Use
    `--disable-thread-pool` with Autotools based build or set
    `LOG4CPLUS_ENABLE_THREAD_POOL` to `OFF` with CMake based build.

  - Improved SONAME handling in CMake.

  - Update Catch to 2.13.4 to fix compilation on MacOS X on AArch64.


-- 
VH

[Log4cplus-devel] [log4cplus:bugs] #335 AsyncAppender leads to memory leaks

[Guglielmo F. <gf...@us...>]

I am observing memory leaks in log4cplus compiled as static library with windows visual studio 2015, since I cannot terminate the thread which needs to run continuosly in a server, should I call log4cplus::threadCleanup() periodically or what ?



---

** [bugs:#335] AsyncAppender leads to memory leaks**

**Status:** open
**Group:** v1.2.0
**Labels:** AsyncAppender memory leaks 
**Created:** Thu Sep 15, 2016 01:34 AM UTC by davy
**Last Updated:** Sun Jan 29, 2017 07:22 PM UTC
**Owner:** Václav Haisman


**When i use the AsyncAppender in V1.2.0, VS2010 had detected many memory leaks like this:**

```
{2713} normal block at 0x00000000039C3070, 40 bytes long. Data: <@ I > 40 8B 49 00 00 00 00 00 FF FF FF FF 00 00 00 00
{2712} normal block at 0x00000000039BE0B0, 72 bytes long. Data: < @ @ > 08 EE 86 40 01 00 00 00 10 EE 86 40 01 00 00 00
{2711} normal block at 0x00000000039C1F40, 40 bytes long. Data: < I > E0 8A 49 00 00 00 00 00 FF FF FF FF 00 00 00 00
{2710} normal block at 0x00000000039BE000, 64 bytes long. Data: <(z @ 8z @ > 28 7A 87 40 01 00 00 00 38 7A 87 40 01 00 00 00
{2709} normal block at 0x00000000039C1ED0, 8 bytes long. Data: < > E4 01 00 00 00 00 00 00
{2708} normal block at 0x00000000039BDA00, 8 bytes long. Data: < > E0 01 00 00 00 00 00 00
{2707} normal block at 0x00000000039C1E40, 40 bytes long. Data: < I > 80 8A 49 00 00 00 00 00 FF FF FF FF 00 00 00 00
{2706} normal block at 0x00000000039BF370, 16 bytes long. Data: < > 18 A2 9B 03 00 00 00 00 00 00 00 00 00 00 00 00
{2705} normal block at 0x00000000039BF2E0, 40 bytes long. Data: < I > 20 8A 49 00 00 00 00 00 FF FF FF FF 00 00 00 00
{2704} normal block at 0x00000000039BA210, 112 bytes long. Data: < @ p > B8 C4 87 40 01 00 00 00 70 F3 9B 03 00 00 00 00
{2701} normal block at 0x00000000039B9300, 8 bytes long. Data: < > 00 00 00 00 00 00 00 00
{2309} normal block at 0x00000000039C1DC0, 16 bytes long. Data: < > 80 A4 9B 03 00 00 00 00 00 00 00 00 00 00 00 00
{2308} normal block at 0x00000000039C1D30, 40 bytes long. Data: <p=E > 70 3D 45 00 00 00 00 00 FF FF FF FF 00 00 00 00
{2307} normal block at 0x00000000039C1CB0, 16 bytes long. Data: < - @ > 88 2D 87 40 01 00 00 00 01 CD CD CD CD CD CD CD
{2306} normal block at 0x00000000039C0E70, 16 bytes long. Data: < > 18 A4 9B 03 00 00 00 00 00 00 00 00 00 00 00 00
{2305} normal block at 0x00000000039C0DF0, 16 bytes long. Data: < @ @ > 90 8C 87 40 01 00 00 00 40 06 9B 03 00 00 00 00
{2304} normal block at 0x00000000039BA540, 40 bytes long. Data: <P<E > 50 3C 45 00 00 00 00 00 FF FF FF FF 00 00 00 00
{2303} normal block at 0x00000000039BA400, 208 bytes long. Data: < | @ H| @ > 08 7C 87 40 01 00 00 00 48 7C 87 40 01 00 00 00
```



---

Sent from sourceforge.net because log...@li... is subscribed to https://sourceforge.net/p/log4cplus/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/log4cplus/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

Re: [Log4cplus-devel] build v2.0.5 with ubuntu 16.04

[Václav H. <vha...@gm...>]

On 11. 04. 20 11:52, ruediger klimt wrote:
> Hi,
> building v2.0.5 with ubuntu 16.04. seems not to work, which probably is
> not a bug, but a desired feature. I have gcc / g++ 7.4.0 installed,
> 
> gcc --version : gcc (Ubuntu 7.4.0-1ubuntu1~16.04~ppa1) 7.4.0
> g++ --version : g++ (Ubuntu 7.4.0-1ubuntu1~16.04~ppa1) 7.4.0
> 
> which should be sufficient for c++17. Executing
> ./scripts/doautoreconf.sh fails with several errors:
> 
> ./scripts/doautoreconf.sh: 27: ./scripts/doautoreconf.sh:
> libtoolize-2.4.6: not found
> ./scripts/doautoreconf.sh: 28: ./scripts/doautoreconf.sh:
> aclocal-1.16.1: not found
> ./scripts/doautoreconf.sh: 29: ./scripts/doautoreconf.sh:
> automake-1.16.1: not found
> ./scripts/doautoreconf.sh: 30: ./scripts/doautoreconf.sh: autoconf-2.69:
> not found
> ./scripts/doautoreconf.sh: 31: ./scripts/doautoreconf.sh: autom4te-2.69:
> not found
> 
> with installed automake tools versions on my ubuntu 16.04. system are :
> 
> libtoolize --version : libtoolize (GNU libtool) 2.4.6
> aclocal --version  :  aclocal (GNU automake) 1.15
> automake --version : automake (GNU automake) 1.15
> autoconf --version  : autoconf (GNU Autoconf) 2.69
> utautom4te --version : autom4te (GNU Autoconf) 2.69oconf) 2.69
> 
> At least the installed libtoolize, autoconf and autom4te should fit the
> required versions. Though doautoreconf.sh fails, running ./configure
> works, but make then fails with
> 
> configure.ac:11: error: require Automake 1.16.1, but have 1.15
> 
> For there is no easy way for updating automake to a higher version under
> ubuntu 16.04, and cmake also fails with errors, is there a way to get
> the current version 2.0.5. to run with ubuntu 16.04 without upgrading to
> ubuntu 18.04. ?
> 
> Best regards
> 

How did you get the source? It should build if it is extracted from
distribution tar.gz. If you are doing a checkout from Git repository
tag, then you have to run the ./scripts/fix-timestamps.sh from the root
of the repo.

-- 
VH

[Log4cplus-devel] build v2.0.5 with ubuntu 16.04

[ruediger k. <rue...@fe...>]

<!doctype html>
<html>
 <head> 
  <meta charset="UTF-8"> 
 </head>
 <body>
  <div>
   Hi,
   <br>
  </div>
  <div>
   building v2.0.5 with ubuntu 16.04. seems not to work, which probably is not a bug, but a desired feature. I have gcc / g++ 7.4.0 installed, 
  </div>
  <div>
   <br>
  </div>
  <div>
   gcc --version : gcc (Ubuntu 7.4.0-1ubuntu1~16.04~ppa1) 7.4.0
   <br>
  </div>
  <div>
   g++ --version : g++ (Ubuntu 7.4.0-1ubuntu1~16.04~ppa1) 7.4.0
   <br>
  </div>
  <div>
   <br>
  </div>
  <div>
   which should be sufficient for c++17. Executing ./scripts/doautoreconf.sh fails with several errors:
  </div>
  <div>
   <br>
  </div>
  <div>
   ./scripts/doautoreconf.sh: 27: ./scripts/doautoreconf.sh: libtoolize-2.4.6: not found
   <br>./scripts/doautoreconf.sh: 28: ./scripts/doautoreconf.sh: aclocal-1.16.1: not found
   <br>./scripts/doautoreconf.sh: 29: ./scripts/doautoreconf.sh: automake-1.16.1: not found
   <br>./scripts/doautoreconf.sh: 30: ./scripts/doautoreconf.sh: autoconf-2.69: not found
   <br>./scripts/doautoreconf.sh: 31: ./scripts/doautoreconf.sh: autom4te-2.69: not found
   <br>
  </div>
  <div>
   <br>
  </div>
  <div>
   with installed automake tools versions on my ubuntu 16.04. system are :
   <br>
  </div>
  <div>
   <br>
  </div>
  <div>
   libtoolize --version : libtoolize (GNU libtool) 2.4.6
   <br>aclocal --version&nbsp; :&nbsp; aclocal (GNU automake) 1.15
   <br>automake --version : automake (GNU automake) 1.15
  </div>
  <div>
   autoconf --version&nbsp; : autoconf (GNU Autoconf) 2.69
   <br>
  </div>
  <div>
   utautom4te --version : autom4te (GNU Autoconf) 2.69oconf) 2.69
  </div>
  <div>
   <br>
  </div>
  <div>
   At least the installed libtoolize, autoconf and autom4te should fit the required versions. Though&nbsp;doautoreconf.sh fails, running ./configure works, but make then fails with
   <br>
  </div>
  <div>
   <br>
  </div>
  <div>
   configure.ac:11: error: require Automake 1.16.1, but have 1.15
   <br>
  </div>
  <div>
   <br>
  </div>
  <div>
   For there is no easy way for updating automake to a higher version under ubuntu 16.04, and cmake also fails with errors, is there a way to get the current version 2.0.5. to run with ubuntu 16.04 without upgrading to ubuntu 18.04. ?
   <br>
  </div>
  <div>
   <br>
  </div>
  <div>
   Best regards
   <br>
  </div> 
 </body>
</html>

[Log4cplus-devel] [log4cplus:bugs] #344 liblog4cplus. a linux library - compilation for std=c++11

[Václav H. <wi...@us...>]

- **status**: open --> not-a-bug
- **assigned_to**: Václav Haisman



---

** [bugs:#344] liblog4cplus. a linux library - compilation for std=c++11**

**Status:** not-a-bug
**Group:** v1.1.3
**Created:** Mon Jul 29, 2019 02:53 PM UTC by Andreea Furnica
**Last Updated:** Mon Jul 29, 2019 04:45 PM UTC
**Owner:** Václav Haisman
**Attachments:**

- [configure](https://sourceforge.net/p/log4cplus/bugs/344/attachment/configure) (788.3 kB; text/plain)


Hello,

I am using a Visual Studio GDB project and I have a problem including the liblog4cplus. a static library in  the linker inputs. 
This are the errors received:

```text
..\..\Dependencies\log4cplus-1.2.1\.libs\liblog4cplus.a(liblog4cplus_la-appender.o): In function `void std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_construct<char*>(char*, char*, std::forward_iterator_tag)':
2>\usr\include\c++\5\bits\basic_string.tcc(223): error : undefined reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_create(unsigned long&, unsigned long)'
2>..\..\..\Dependencies\log4cplus-1.2.1\.libs\liblog4cplus.a(liblog4cplus_la-appender.o): In function `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::operator=(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&&)':
2>\usr\include\c++\5\bits\basic_string.h(589): error : undefined reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::swap(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&)'
```

It seems that the library is not recognised as being compiled with -std=c++11 

In order compile the library with c++11 I added the command -std=c++11 in the configure file(CXXFLAGS = "-std=c++11") 
This are the parts from configure file which I changed:

```sh
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_cxx_compiler_gnu" >&5
$as_echo "$ac_cv_cxx_compiler_gnu" >&6; }
if test $ac_compiler_gnu = yes; then
  GXX=yes
else
  GXX=
fi
ac_test_CXXFLAGS=${CXXFLAGS+set}
ac_save_CXXFLAGS=$CXXFLAGS
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether $CXX accepts -g" >&5
$as_echo_n "checking whether $CXX accepts -g... " >&6; }
if ${ac_cv_prog_cxx_g+:} false; then :
  $as_echo_n "(cached) " >&6
else
  ac_save_cxx_werror_flag=$ac_cxx_werror_flag
   ac_cxx_werror_flag=yes
   ac_cv_prog_cxx_g=no
   CXXFLAGS="-g -std=c++11"
   cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h.  */

int
main ()
{

  ;
  return 0;
}
_ACEOF
if ac_fn_cxx_try_compile "$LINENO"; then :
  ac_cv_prog_cxx_g=yes
else
  CXXFLAGS="-std=c++11"
      cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h.  */

int
main ()
{

  ;
  return 0;
}
_ACEOF
if ac_fn_cxx_try_compile "$LINENO"; then :

else
  ac_cxx_werror_flag=$ac_save_cxx_werror_flag
	 CXXFLAGS="-g -std=c++11"
	 cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h.  */

int
main ()
{

  ;
  return 0;
}
_ACEOF
if ac_fn_cxx_try_compile "$LINENO"; then :
  ac_cv_prog_cxx_g=yes
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
   ac_cxx_werror_flag=$ac_save_cxx_werror_flag
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cxx_g" >&5
$as_echo "$ac_cv_prog_cxx_g" >&6; }
if test "$ac_test_CXXFLAGS" = set; then
  CXXFLAGS=$ac_save_CXXFLAGS
elif test $ac_cv_prog_cxx_g = yes; then
  if test "$GXX" = yes; then
    CXXFLAGS="-g -O2 -std=c++11"
  else
    CXXFLAGS="-g -std=c++11"
  fi
else
  if test "$GXX" = yes; then
    CXXFLAGS="-O2 -std=c++11"
  else
    CXXFLAGS="-std=c++11"
  fi
fi
```

The commad used to compile the library is:
sudo ./configure --enable-static

The compilation worked well.

I am using the log4cpuls 1.2.1 version and the gcc-5.4.0 version to compile the library.
I think the error from visual studio is related to c++11 compilation. 
Could you please tell me if the compilation procedure is ok?
If not, please tell which is the right procedure to compile the library for c++11?
Does the errors mean somenthing else?
Please find attached the configure file/



---

Sent from sourceforge.net because log...@li... is subscribed to https://sourceforge.net/p/log4cplus/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/log4cplus/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Log4cplus-devel] log4cplus 2.0.5

[Václav H. <vha...@gm...>]

Hi.

I have released log4cplus 2.0.5. This is maintenance release.

  *

    Modernized CMake build.

  *

    Update iOS support to build for current hardware architectures.
    (Patch by Pawel Maczewski)

  *

    Fix issue with |std::va_list| value reuse.

  *

    Fix parsing of |include| in configuration when included file path
    contains |=|. (Patch by Peter Pei)

  *

    Fix build issue #455. Source file |callbackappender.cxx| is missing
    from Visual Studio project for static library.

  *

    Fix issue #415. Wrong base source file name is provided if path on
    Windows contains |/|.

  *

    Change of default behaviour: Instantiate thread pool with only 4
    threads.


-- 
VH

[Log4cplus-devel] [log4cplus:bugs] #344 liblog4cplus. a linux library - compilation for std=c++11

[Václav H. <wi...@us...>]

- Description has changed:

Diff:

~~~~

--- old
+++ new
@@ -3,7 +3,7 @@
 I am using a Visual Studio GDB project and I have a problem including the liblog4cplus. a static library in  the linker inputs. 
 This are the errors received:
 
-```
+```text
 ..\..\Dependencies\log4cplus-1.2.1\.libs\liblog4cplus.a(liblog4cplus_la-appender.o): In function `void std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_construct<char*>(char*, char*, std::forward_iterator_tag)':
 2>\usr\include\c++\5\bits\basic_string.tcc(223): error : undefined reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_create(unsigned long&, unsigned long)'
 2>..\..\..\Dependencies\log4cplus-1.2.1\.libs\liblog4cplus.a(liblog4cplus_la-appender.o): In function `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::operator=(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&&)':
@@ -15,7 +15,7 @@
 In order compile the library with c++11 I added the command -std=c++11 in the configure file(CXXFLAGS = "-std=c++11") 
 This are the parts from configure file which I changed:
 
-```
+```sh
 fi
 { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_cxx_compiler_gnu" >&5
 $as_echo "$ac_cv_cxx_compiler_gnu" >&6; }

~~~~




---

** [bugs:#344] liblog4cplus. a linux library - compilation for std=c++11**

**Status:** open
**Group:** v1.1.3
**Created:** Mon Jul 29, 2019 02:53 PM UTC by Andreea Furnica
**Last Updated:** Mon Jul 29, 2019 04:43 PM UTC
**Owner:** nobody
**Attachments:**

- [configure](https://sourceforge.net/p/log4cplus/bugs/344/attachment/configure) (788.3 kB; text/plain)


Hello,

I am using a Visual Studio GDB project and I have a problem including the liblog4cplus. a static library in  the linker inputs. 
This are the errors received:

```text
..\..\Dependencies\log4cplus-1.2.1\.libs\liblog4cplus.a(liblog4cplus_la-appender.o): In function `void std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_construct<char*>(char*, char*, std::forward_iterator_tag)':
2>\usr\include\c++\5\bits\basic_string.tcc(223): error : undefined reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_create(unsigned long&, unsigned long)'
2>..\..\..\Dependencies\log4cplus-1.2.1\.libs\liblog4cplus.a(liblog4cplus_la-appender.o): In function `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::operator=(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&&)':
2>\usr\include\c++\5\bits\basic_string.h(589): error : undefined reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::swap(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&)'
```

It seems that the library is not recognised as being compiled with -std=c++11 

In order compile the library with c++11 I added the command -std=c++11 in the configure file(CXXFLAGS = "-std=c++11") 
This are the parts from configure file which I changed:

```sh
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_cxx_compiler_gnu" >&5
$as_echo "$ac_cv_cxx_compiler_gnu" >&6; }
if test $ac_compiler_gnu = yes; then
  GXX=yes
else
  GXX=
fi
ac_test_CXXFLAGS=${CXXFLAGS+set}
ac_save_CXXFLAGS=$CXXFLAGS
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether $CXX accepts -g" >&5
$as_echo_n "checking whether $CXX accepts -g... " >&6; }
if ${ac_cv_prog_cxx_g+:} false; then :
  $as_echo_n "(cached) " >&6
else
  ac_save_cxx_werror_flag=$ac_cxx_werror_flag
   ac_cxx_werror_flag=yes
   ac_cv_prog_cxx_g=no
   CXXFLAGS="-g -std=c++11"
   cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h.  */

int
main ()
{

  ;
  return 0;
}
_ACEOF
if ac_fn_cxx_try_compile "$LINENO"; then :
  ac_cv_prog_cxx_g=yes
else
  CXXFLAGS="-std=c++11"
      cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h.  */

int
main ()
{

  ;
  return 0;
}
_ACEOF
if ac_fn_cxx_try_compile "$LINENO"; then :

else
  ac_cxx_werror_flag=$ac_save_cxx_werror_flag
	 CXXFLAGS="-g -std=c++11"
	 cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h.  */

int
main ()
{

  ;
  return 0;
}
_ACEOF
if ac_fn_cxx_try_compile "$LINENO"; then :
  ac_cv_prog_cxx_g=yes
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
   ac_cxx_werror_flag=$ac_save_cxx_werror_flag
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cxx_g" >&5
$as_echo "$ac_cv_prog_cxx_g" >&6; }
if test "$ac_test_CXXFLAGS" = set; then
  CXXFLAGS=$ac_save_CXXFLAGS
elif test $ac_cv_prog_cxx_g = yes; then
  if test "$GXX" = yes; then
    CXXFLAGS="-g -O2 -std=c++11"
  else
    CXXFLAGS="-g -std=c++11"
  fi
else
  if test "$GXX" = yes; then
    CXXFLAGS="-O2 -std=c++11"
  else
    CXXFLAGS="-std=c++11"
  fi
fi
```

The commad used to compile the library is:
sudo ./configure --enable-static

The compilation worked well.

I am using the log4cpuls 1.2.1 version and the gcc-5.4.0 version to compile the library.
I think the error from visual studio is related to c++11 compilation. 
Could you please tell me if the compilation procedure is ok?
If not, please tell which is the right procedure to compile the library for c++11?
Does the errors mean somenthing else?
Please find attached the configure file/



---

Sent from sourceforge.net because log...@li... is subscribed to https://sourceforge.net/p/log4cplus/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/log4cplus/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Log4cplus-devel] [log4cplus:bugs] #344 liblog4cplus. a linux library - compilation for std=c++11

[Václav H. <wi...@us...>]

For 1.2.1, the decision how to compile log4cplus, whether to use C++03 or C++11 is yours. It can be compiled either way. Generally, if you want to change `CXXFLAGS` you can do so on `configure` script command line by simply adding `CXXFLAGS="-std=c++11"` to its command line.


---

** [bugs:#344] liblog4cplus. a linux library - compilation for std=c++11**

**Status:** open
**Group:** v1.1.3
**Created:** Mon Jul 29, 2019 02:53 PM UTC by Andreea Furnica
**Last Updated:** Mon Jul 29, 2019 04:39 PM UTC
**Owner:** nobody
**Attachments:**

- [configure](https://sourceforge.net/p/log4cplus/bugs/344/attachment/configure) (788.3 kB; text/plain)


Hello,

I am using a Visual Studio GDB project and I have a problem including the liblog4cplus. a static library in  the linker inputs. 
This are the errors received:

```
..\..\Dependencies\log4cplus-1.2.1\.libs\liblog4cplus.a(liblog4cplus_la-appender.o): In function `void std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_construct<char*>(char*, char*, std::forward_iterator_tag)':
2>\usr\include\c++\5\bits\basic_string.tcc(223): error : undefined reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_create(unsigned long&, unsigned long)'
2>..\..\..\Dependencies\log4cplus-1.2.1\.libs\liblog4cplus.a(liblog4cplus_la-appender.o): In function `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::operator=(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&&)':
2>\usr\include\c++\5\bits\basic_string.h(589): error : undefined reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::swap(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&)'
```

It seems that the library is not recognised as being compiled with -std=c++11 

In order compile the library with c++11 I added the command -std=c++11 in the configure file(CXXFLAGS = "-std=c++11") 
This are the parts from configure file which I changed:

```
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_cxx_compiler_gnu" >&5
$as_echo "$ac_cv_cxx_compiler_gnu" >&6; }
if test $ac_compiler_gnu = yes; then
  GXX=yes
else
  GXX=
fi
ac_test_CXXFLAGS=${CXXFLAGS+set}
ac_save_CXXFLAGS=$CXXFLAGS
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether $CXX accepts -g" >&5
$as_echo_n "checking whether $CXX accepts -g... " >&6; }
if ${ac_cv_prog_cxx_g+:} false; then :
  $as_echo_n "(cached) " >&6
else
  ac_save_cxx_werror_flag=$ac_cxx_werror_flag
   ac_cxx_werror_flag=yes
   ac_cv_prog_cxx_g=no
   CXXFLAGS="-g -std=c++11"
   cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h.  */

int
main ()
{

  ;
  return 0;
}
_ACEOF
if ac_fn_cxx_try_compile "$LINENO"; then :
  ac_cv_prog_cxx_g=yes
else
  CXXFLAGS="-std=c++11"
      cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h.  */

int
main ()
{

  ;
  return 0;
}
_ACEOF
if ac_fn_cxx_try_compile "$LINENO"; then :

else
  ac_cxx_werror_flag=$ac_save_cxx_werror_flag
	 CXXFLAGS="-g -std=c++11"
	 cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h.  */

int
main ()
{

  ;
  return 0;
}
_ACEOF
if ac_fn_cxx_try_compile "$LINENO"; then :
  ac_cv_prog_cxx_g=yes
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
   ac_cxx_werror_flag=$ac_save_cxx_werror_flag
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cxx_g" >&5
$as_echo "$ac_cv_prog_cxx_g" >&6; }
if test "$ac_test_CXXFLAGS" = set; then
  CXXFLAGS=$ac_save_CXXFLAGS
elif test $ac_cv_prog_cxx_g = yes; then
  if test "$GXX" = yes; then
    CXXFLAGS="-g -O2 -std=c++11"
  else
    CXXFLAGS="-g -std=c++11"
  fi
else
  if test "$GXX" = yes; then
    CXXFLAGS="-O2 -std=c++11"
  else
    CXXFLAGS="-std=c++11"
  fi
fi
```

The commad used to compile the library is:
sudo ./configure --enable-static

The compilation worked well.

I am using the log4cpuls 1.2.1 version and the gcc-5.4.0 version to compile the library.
I think the error from visual studio is related to c++11 compilation. 
Could you please tell me if the compilation procedure is ok?
If not, please tell which is the right procedure to compile the library for c++11?
Does the errors mean somenthing else?
Please find attached the configure file/



---

Sent from sourceforge.net because log...@li... is subscribed to https://sourceforge.net/p/log4cplus/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/log4cplus/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Log4cplus-devel] [log4cplus:bugs] #344 liblog4cplus. a linux library - compilation for std=c++11

[Václav H. <wi...@us...>]

- Description has changed:

Diff:

~~~~

--- old
+++ new
@@ -2,17 +2,20 @@
 
 I am using a Visual Studio GDB project and I have a problem including the liblog4cplus. a static library in  the linker inputs. 
 This are the errors received:
+
+```
 ..\..\Dependencies\log4cplus-1.2.1\.libs\liblog4cplus.a(liblog4cplus_la-appender.o): In function `void std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_construct<char*>(char*, char*, std::forward_iterator_tag)':
 2>\usr\include\c++\5\bits\basic_string.tcc(223): error : undefined reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_create(unsigned long&, unsigned long)'
 2>..\..\..\Dependencies\log4cplus-1.2.1\.libs\liblog4cplus.a(liblog4cplus_la-appender.o): In function `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::operator=(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&&)':
 2>\usr\include\c++\5\bits\basic_string.h(589): error : undefined reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::swap(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&)'
-
+```
 
 It seems that the library is not recognised as being compiled with -std=c++11 
 
 In order compile the library with c++11 I added the command -std=c++11 in the configure file(CXXFLAGS = "-std=c++11") 
 This are the parts from configure file which I changed:
 
+```
 fi
 { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_cxx_compiler_gnu" >&5
 $as_echo "$ac_cv_cxx_compiler_gnu" >&6; }
@@ -101,6 +104,7 @@
     CXXFLAGS="-std=c++11"
   fi
 fi
+```
 
 The commad used to compile the library is:
 sudo ./configure --enable-static

~~~~




---

** [bugs:#344] liblog4cplus. a linux library - compilation for std=c++11**

**Status:** open
**Group:** v1.1.3
**Created:** Mon Jul 29, 2019 02:53 PM UTC by Andreea Furnica
**Last Updated:** Mon Jul 29, 2019 02:53 PM UTC
**Owner:** nobody
**Attachments:**

- [configure](https://sourceforge.net/p/log4cplus/bugs/344/attachment/configure) (788.3 kB; text/plain)


Hello,

I am using a Visual Studio GDB project and I have a problem including the liblog4cplus. a static library in  the linker inputs. 
This are the errors received:

```
..\..\Dependencies\log4cplus-1.2.1\.libs\liblog4cplus.a(liblog4cplus_la-appender.o): In function `void std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_construct<char*>(char*, char*, std::forward_iterator_tag)':
2>\usr\include\c++\5\bits\basic_string.tcc(223): error : undefined reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_create(unsigned long&, unsigned long)'
2>..\..\..\Dependencies\log4cplus-1.2.1\.libs\liblog4cplus.a(liblog4cplus_la-appender.o): In function `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::operator=(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&&)':
2>\usr\include\c++\5\bits\basic_string.h(589): error : undefined reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::swap(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&)'
```

It seems that the library is not recognised as being compiled with -std=c++11 

In order compile the library with c++11 I added the command -std=c++11 in the configure file(CXXFLAGS = "-std=c++11") 
This are the parts from configure file which I changed:

```
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_cxx_compiler_gnu" >&5
$as_echo "$ac_cv_cxx_compiler_gnu" >&6; }
if test $ac_compiler_gnu = yes; then
  GXX=yes
else
  GXX=
fi
ac_test_CXXFLAGS=${CXXFLAGS+set}
ac_save_CXXFLAGS=$CXXFLAGS
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether $CXX accepts -g" >&5
$as_echo_n "checking whether $CXX accepts -g... " >&6; }
if ${ac_cv_prog_cxx_g+:} false; then :
  $as_echo_n "(cached) " >&6
else
  ac_save_cxx_werror_flag=$ac_cxx_werror_flag
   ac_cxx_werror_flag=yes
   ac_cv_prog_cxx_g=no
   CXXFLAGS="-g -std=c++11"
   cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h.  */

int
main ()
{

  ;
  return 0;
}
_ACEOF
if ac_fn_cxx_try_compile "$LINENO"; then :
  ac_cv_prog_cxx_g=yes
else
  CXXFLAGS="-std=c++11"
      cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h.  */

int
main ()
{

  ;
  return 0;
}
_ACEOF
if ac_fn_cxx_try_compile "$LINENO"; then :

else
  ac_cxx_werror_flag=$ac_save_cxx_werror_flag
	 CXXFLAGS="-g -std=c++11"
	 cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h.  */

int
main ()
{

  ;
  return 0;
}
_ACEOF
if ac_fn_cxx_try_compile "$LINENO"; then :
  ac_cv_prog_cxx_g=yes
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
   ac_cxx_werror_flag=$ac_save_cxx_werror_flag
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cxx_g" >&5
$as_echo "$ac_cv_prog_cxx_g" >&6; }
if test "$ac_test_CXXFLAGS" = set; then
  CXXFLAGS=$ac_save_CXXFLAGS
elif test $ac_cv_prog_cxx_g = yes; then
  if test "$GXX" = yes; then
    CXXFLAGS="-g -O2 -std=c++11"
  else
    CXXFLAGS="-g -std=c++11"
  fi
else
  if test "$GXX" = yes; then
    CXXFLAGS="-O2 -std=c++11"
  else
    CXXFLAGS="-std=c++11"
  fi
fi
```

The commad used to compile the library is:
sudo ./configure --enable-static

The compilation worked well.

I am using the log4cpuls 1.2.1 version and the gcc-5.4.0 version to compile the library.
I think the error from visual studio is related to c++11 compilation. 
Could you please tell me if the compilation procedure is ok?
If not, please tell which is the right procedure to compile the library for c++11?
Does the errors mean somenthing else?
Please find attached the configure file/



---

Sent from sourceforge.net because log...@li... is subscribed to https://sourceforge.net/p/log4cplus/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/log4cplus/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Log4cplus-devel] [log4cplus:bugs] #344 liblog4cplus. a linux library - compilation for std=c++11

[Andreea F. <and...@us...>]

---

** [bugs:#344] liblog4cplus. a linux library - compilation for std=c++11**

**Status:** open
**Group:** v1.1.3
**Created:** Mon Jul 29, 2019 02:53 PM UTC by Andreea Furnica
**Last Updated:** Mon Jul 29, 2019 02:53 PM UTC
**Owner:** nobody
**Attachments:**

- [configure](https://sourceforge.net/p/log4cplus/bugs/344/attachment/configure) (788.3 kB; text/plain)


Hello,

I am using a Visual Studio GDB project and I have a problem including the liblog4cplus. a static library in  the linker inputs. 
This are the errors received:
..\..\Dependencies\log4cplus-1.2.1\.libs\liblog4cplus.a(liblog4cplus_la-appender.o): In function `void std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_construct<char*>(char*, char*, std::forward_iterator_tag)':
2>\usr\include\c++\5\bits\basic_string.tcc(223): error : undefined reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_create(unsigned long&, unsigned long)'
2>..\..\..\Dependencies\log4cplus-1.2.1\.libs\liblog4cplus.a(liblog4cplus_la-appender.o): In function `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::operator=(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&&)':
2>\usr\include\c++\5\bits\basic_string.h(589): error : undefined reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::swap(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&)'


It seems that the library is not recognised as being compiled with -std=c++11 

In order compile the library with c++11 I added the command -std=c++11 in the configure file(CXXFLAGS = "-std=c++11") 
This are the parts from configure file which I changed:

fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_cxx_compiler_gnu" >&5
$as_echo "$ac_cv_cxx_compiler_gnu" >&6; }
if test $ac_compiler_gnu = yes; then
  GXX=yes
else
  GXX=
fi
ac_test_CXXFLAGS=${CXXFLAGS+set}
ac_save_CXXFLAGS=$CXXFLAGS
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether $CXX accepts -g" >&5
$as_echo_n "checking whether $CXX accepts -g... " >&6; }
if ${ac_cv_prog_cxx_g+:} false; then :
  $as_echo_n "(cached) " >&6
else
  ac_save_cxx_werror_flag=$ac_cxx_werror_flag
   ac_cxx_werror_flag=yes
   ac_cv_prog_cxx_g=no
   CXXFLAGS="-g -std=c++11"
   cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h.  */

int
main ()
{

  ;
  return 0;
}
_ACEOF
if ac_fn_cxx_try_compile "$LINENO"; then :
  ac_cv_prog_cxx_g=yes
else
  CXXFLAGS="-std=c++11"
      cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h.  */

int
main ()
{

  ;
  return 0;
}
_ACEOF
if ac_fn_cxx_try_compile "$LINENO"; then :

else
  ac_cxx_werror_flag=$ac_save_cxx_werror_flag
	 CXXFLAGS="-g -std=c++11"
	 cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h.  */

int
main ()
{

  ;
  return 0;
}
_ACEOF
if ac_fn_cxx_try_compile "$LINENO"; then :
  ac_cv_prog_cxx_g=yes
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
   ac_cxx_werror_flag=$ac_save_cxx_werror_flag
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cxx_g" >&5
$as_echo "$ac_cv_prog_cxx_g" >&6; }
if test "$ac_test_CXXFLAGS" = set; then
  CXXFLAGS=$ac_save_CXXFLAGS
elif test $ac_cv_prog_cxx_g = yes; then
  if test "$GXX" = yes; then
    CXXFLAGS="-g -O2 -std=c++11"
  else
    CXXFLAGS="-g -std=c++11"
  fi
else
  if test "$GXX" = yes; then
    CXXFLAGS="-O2 -std=c++11"
  else
    CXXFLAGS="-std=c++11"
  fi
fi

The commad used to compile the library is:
sudo ./configure --enable-static

The compilation worked well.

I am using the log4cpuls 1.2.1 version and the gcc-5.4.0 version to compile the library.
I think the error from visual studio is related to c++11 compilation. 
Could you please tell me if the compilation procedure is ok?
If not, please tell which is the right procedure to compile the library for c++11?
Does the errors mean somenthing else?
Please find attached the configure file/



---

Sent from sourceforge.net because log...@li... is subscribed to https://sourceforge.net/p/log4cplus/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/log4cplus/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Log4cplus-devel] log4cplus 2.0.4 released

[Václav H. <vha...@gm...>]

Hi.

I have released log4cplus 2.0.4. This is maintenance release.

  - Fix Catch2 include path. GitHub issue #379.

  - Disable POSIX signals reception in thread before creating pool
    threads. GitHub issue #385 and follow up issue #390.

  - Fix compilation with NVCC in CUDA mode. GitHub issue #375.

  - Fix compilation with Visual Studio in C++17 mode. GitHub issue #401.

  - Allow disabling implicit initialization through `configure` script
    option `--disable-implicit-initialization`, or CMake build option
    `LOG4CPLUS_REQUIRE_EXPLICIT_INITIALIZATION`. (MaksymB)

  - Remove `android` directory with obsolete Android support. GitHub
    issue #283.

  - Link with `libatomic` when necessary. (Fabrice Fontaine)


-- 
VH

[Log4cplus-devel] log4cplus 1.2.2 released

[Václav H. <vha...@gm...>]

I have released log4cplus 1.2.2. It is small bugfix release:

  *

    GitHub issue #375. Fixed compilation with NVCC in CUDA mode.

  *

    Small documentation tweaks.

​

-- 
VH

[Log4cplus-devel] log4cplus 2.0.3 released

[Václav H. <vha...@gm...>]

I have released log4cplus 2.0.3:

  *

    Fix compilation on systems without |O_CLOEXEC|. This affects, e.g.,
    Solaris 10. GitHub issue #326. (Patch by Jiangrz).

  *

    Provide |log4cplus::deinitialize()| to make the API symmetric
    (|log4cplus::initialize()| already exists) and to allow
    de-/initialization without |log4cplus::Initializer| instance. GitHub
    issue #340.

  *

    Deal with |register| keyword being generated in SWIG based bindings.
    The keyword is unused and reserved in C++17. Remove use of
    |std::unary_function|, it was removed in C++17.

  *

    Add ability to define new log levels using C API. Add
    reconfiguration API. (Jens Rehsack)

  *

    Add |NDCMatchFilter| and |MDCMatchFilter|. (Franck)

​

-- 
VH

[Log4cplus-devel] log4cplus 2.0.2 released

[Václav H. <vha...@gm...>]

I have released log4cplus 2.0.2. It is mostly bug fixing release:

  *

    Allow setting thread pool size using new function
    |setThreadPoolSize()|. Allow setting the size from
    |log4cplus.properties| using |log4cplus.threadPoolSize| property.
    Lower initial thread pool size by half to
    |std::thread::hardware_concurrency()| threads. GitHub issue #315.

  *

    Fix Autotools based build for MinGW. GitHub issue #317.

  *

    Add |configure| script option |--enable-lto| to allow easier LTO builds.

  *

    Optimization of |getFormattedTime()|. (Alexey Vishtak)

  *

    Introduction of |LOG4CPLUS_MACRO_FILE()| used in logging macros to
    allow users to redefine it and consequently hide source file names
    from their compiled executables and logging output.

​

-- 
VH

[Log4cplus-devel] log4cplus 2.0.1 released

[Václav H. <vha...@gm...>]

I have release log4cplus 2.0.1. There are few minor changes:

  * Update to Automake 1.16.1.
  * Adjust |spi::LoggerFactory| to allow custom |spi::LoggerImpl|.
    GitHub issue #309.
  * Fix MacOS X compilation. GitHub issue #312.

​

-- 
VH

Re: [Log4cplus-devel] [log4cplus] testsuite: 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 failed

[Hilton F. <hil...@gm...>]

Hello, Václav !

Sorry to worry you. In the weekend I will test everything again in Debian
9.40, and maybe I will reinstall WSL, aka Linux Subsystem for Windows.

This execution came from an Ubuntu under a Windows 10 that I use at work. I
suppose that Ubuntu is not as native as we would like it to be.

Please don't be upset. Your code looks great, but as you certainly know by
now, Windows 10 sometimes can play nasty practical jokes on the poor
programmers and users.

All the best,
Hilton

On Wed, May 9, 2018 at 5:00 PM, Václav Haisman <vha...@gm...> wrote:

>
>
> On 9 May 2018 at 02:09, Hilton Fernandes <hil...@gm...>
> wrote:
>
>> Dear all,
>>
>> I would like to work with log4cplus, but I'm facing some problems.
>>
>> Please find attached the result of the tests, as you asked for.
>>
>> I have copied ThreadPool.h from your project to the directory threadpool
>> in log4cplus folder.
>>
>> Then I did a simple configure, with
>>
>> ./configure --enable-debug
>>
>> followed by the default make:
>> make
>>
>> and then
>> make check
>>
>> All the best,
>> Hilton
>>
>>
> ​Basically, all of the execution tests have failed.​
>
> ​I have no idea what is going on. Is that the Ubuntu on Windows thing?
>
> --
> VH
>

Re: [Log4cplus-devel] [log4cplus] testsuite: 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 failed

[Václav H. <vha...@gm...>]

On 9 May 2018 at 02:09, Hilton Fernandes <hil...@gm...> wrote:

> Dear all,
>
> I would like to work with log4cplus, but I'm facing some problems.
>
> Please find attached the result of the tests, as you asked for.
>
> I have copied ThreadPool.h from your project to the directory threadpool
> in log4cplus folder.
>
> Then I did a simple configure, with
>
> ./configure --enable-debug
>
> followed by the default make:
> make
>
> and then
> make check
>
> All the best,
> Hilton
>
>
​Basically, all of the execution tests have failed.​

​I have no idea what is going on. Is that the Ubuntu on Windows thing?

-- 
VH

[Log4cplus-devel] [log4cplus] testsuite: 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 failed

[Hilton F. <hil...@gm...>]

 Dear all,

I would like to work with log4cplus, but I'm facing some problems.

Please find attached the result of the tests, as you asked for.

I have copied ThreadPool.h from your project to the directory threadpool in
log4cplus folder.

Then I did a simple configure, with

./configure --enable-debug

followed by the default make:
make

and then
make check

All the best,
Hilton

[Log4cplus-devel] log4cplus 2.0.0 released

[Václav H. <vha...@gm...>]

I have released log4cplus version 2.0.0. There are only minor changes
compared to last release candidate:

  - CMake improvements: Automate export of includes if building as Cmake
sub-module. (Rodion Malinovsky)

  - Debian spec file improvements: Use parallel build. Fix installation
path on 64bit. (Michal Marek)

  - CMake improvements: Use `${CMAKE_INSTALL_LIBDIR}` instead of
hardcoding lib. (Radek Dostál)

  - Experimental Windows 10 ARM support through CMAKE


-- 
VH