log4cplus-devel — Mailing list for log4cplus developers

Re: [Log4cplus-devel] [QUESTION]About tools to build log4cplus

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

On 10/30/2013 12:45 PM, Zhen Ren wrote:
> Hi all,
> I noticed that log4cplus project source direcotry has *CMakeLists.txt*,
> *Makefile.am*,*Makefile.in* and so on.
> 
> As far as I known, cmake is diferent with autotools command like
> aclocal,autoconf,automake etc.So, why our project has both of them?
It actually has three build systems. There are also the Visual Studio
project files.

There are Visual Studio 2010 project files for people with Visual Studio
2010 and later. There is the CMake based build system for other people
on Windows who use things like Code::Blocks or MinGW, etc. The CMake
based build system is also used by Android people and others who
integrate log4cplus compilation into larger projects. Then there is the
Autotools based build system for most people on Unix-like platforms.

> 
> On earth, this project use which tools to build, or both?
> and what is the procedure to build this project? 
Use whichever build system suits you the best. Read README for configure
script options, if you choose to use it.

> 
> I am not sure where this is a silly question, but for me, it is a problem.
> Any idea to help me understand it is appreciated.
> Thanks:)

-- 
VZ

[Log4cplus-devel] [QUESTION]About tools to build log4cplus

[Zhen R. <ren...@gm...>]

Hi all,
I noticed that log4cplus project source direcotry has *CMakeLists.txt*,
*Makefile.am*,*Makefile.in* and so on.

As far as I known, cmake is diferent with autotools command like
aclocal,autoconf,automake etc.So, why our project has both of them?

On earth, this project use which tools to build, or both?
and what is the procedure to build this project?

I am not sure where this is a silly question, but for me, it is a problem.
Any idea to help me understand it is appreciated.
Thanks:)
-- 
Ren Zhen

[Log4cplus-devel] [QUESTION]About tools to build log4cplus

[Zhen R. <ren...@gm...>]

Hi all,
I noticed that log4cplus project source direcotry has *CMakeLists.txt*,
*Makefile.am*,*Makefile.in* and so on.

As far as I known, cmake is diferent with autotools command like
aclocal,autoconf,automake etc.So, why our project has both of them?

On earth, this project use which tools to build, or both?
and what is the procedure to build this project?

I am not sure where this is a silly question, but for me, it is a problem.
Any idea to help me understand it is appreciated.
Thanks:)
-- 
Ren Zhen

Re: [Log4cplus-devel] [Question]: About Function 'initialize' in every log4cplus example code

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

On 23 October 2013 10:13, Zhen Ren wrote:
> Hi all,
> I am learning to use log4cplus example code.
>
> Notice that every example starts with Func 'initialize', And I want to know
> what it do
> for us, why it apears with form of Funtion instead of Class method. I looked
> for it in API Doc, but cannot get any information.
>
> Anyone know it?please give me some help.
The log4cplus::initialize() function is there to initialize the whole
log4cplus library. In most usual cases, on both Windows and Unix--like
platforms, it will be called for you. Unfortunately, there are cases
when it will not be called automatically. This can happen if you are
using static library log4cplus and static C and C++ run time
libraries. It is safe to call the function multiple times before you
use anything else from log4cplus. It is not safe to call the function
from different threads, there is no locking. The assumption is that,
at the worst case, you will call the function at the top of main().

-- 
VZ

[Log4cplus-devel] [Question]: About Function 'initialize' in every log4cplus example code

[Zhen R. <ren...@gm...>]

Hi all,
I am learning to use log4cplus example code.

Notice that every example starts with Func 'initialize', And I want to know
what it do
for us, why it apears with form of Funtion instead of Class method. I
looked for it in API Doc, but cannot get any information.

Anyone know it?please give me some help.

Thanks.
-- 
Ren Zhen

[Log4cplus-devel] log4cplus 1.1.2 released

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

Hi.

I have released log4cplus 1.1.2. There are only few changes since 1.1.2-RC3:

- Added AbstractSocket::shutdown().

- Added missing documentation of MDC pattern layout converter.

- Fixed bug #278 - TLS key leak.

- Implemented %E{ENVVAR} pattern layout formatter for expansion of
environment variables.

-- 
VZ

Re: [Log4cplus-devel] shutdown patch

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

On 10 October 2013 17:36, palladin <p-a...@ya...> wrote:
> Hi Václav,
> one more attempt with shutdown patch.
> Sincerely,Taras.
I have committed your patch with some small changes and additions. I
am attaching diff of the committed. I will push it to repository later
today.

-- 
VZ

[Log4cplus-devel] shutdown patch

[palladin <p-a...@ya...>]

Hi Václav,
one more attempt with shutdown patch.
Sincerely,Taras.

Re: [Log4cplus-devel] Socket close hangs

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

On 09/20/2013 05:07 PM, palladin wrote:
> On 09/19/2013 01:15 AM, Václav Zeman wrote:
>> On 09/18/2013 09:51 AM, palladin wrote:
>>> Dear log4cplus devels,
>>> log4cplus 1.1.1-RC4
>>> <https://sourceforge.net/projects/log4cplus/files/log4cplus-stable/1.1.1/>
>>> Linux version 2.6.32-279.22.1.37.0.el6.x86_64 (abuild@noriko) (gcc
>>> version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) )
>>>
>>> My application has hung after it have used log4cplus::helpers::Socket
>>> from  log4cplus::helpers::ServerSocket::accept,e.g.
>>> log4cplus::helpers::Socket clientSocket = mServerSocket.accept();
>>> clientSocket was put into log4cplus::thread::AbstractThread worker.
>>> Client socket was used in AbstractThread like Socket::read - this is
>>> blocking call and the root of issue.
>>>
>>> Then my application worked for some time  and at the end I did
>>> clientSocket.close() from main thread.
>>> Due to the fact that log4cplus::helpers::Socket::read is blocking call -
>>> my application has hung on AbstractThread::join call.
>>>
>>> I would like to suggest a fiew fixes to this issue:
>>> 1) add non-blocking stuff to log4cplus::helpers::Socket - select or poll.
>>> 2) add to log4cplus::helpers::Socket interface system call shutdown( man
>>> 2 shutdown ).
>> Closing a socket from one thread when the socket is blocked on any
>> operation in another thread is AFAIK very unportable.
>>
>> This could be solved in a way similar to how I have done
>> ServerSocket::accept(), which is indeed using poll() to wait for either
>> an incoming connection or some data arriving to a special interrupt pipe.
>>
>> Also, these helpers are there to help log4cplus. They are not there to
>> be used as public networking framework/API, so fixing this has a low
>> priority for me right now. OTOH, I am open to accepting reasonable patches.
>>
> 
> Dear Václav,
> I prefer your solution in ServerSocket interruption. So could you please
> take a look on provided patch?
> 
> Sincerely ,
> Taras
TBH, I do not like the patch that much. I see several problems:

- It does not take Windows into consideration.
- the MAX() macro instead of std::max function
- use of select() instead of poll()
- I would rather like to see the interruptibility implemented in
existing sockets classes rather than in new kind of socket
InterruptableSocket.
- It lacks error handling at few places.

-- 
VZ

[Log4cplus-devel] Socket close hangs

[palladin <p-a...@ya...>]

Dear log4cplus devels,
I have reported about log4cplus::helpers::Socket hang, also I have 
provided patch to resolve this issue.
Could you please advise if this patch can be applied?

Sincerely,
Taras Shypytiak.

Re: [Log4cplus-devel] Failed to compile with flag "-std=c++11" in projects

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

What was the configure script  command line? You have to compile
log4cplus with C++11 support enabled. Add CXXFLAGS="-std=c++11" to its
command line.

On 06/10/2013, Delian Xu <del...@gm...> wrote:
> Hello,
>
> How to make log4cplus work with compile-flag "-std=c++11" ?
>
> It seems that log4cplus can work with c++11, but I failed to try it, please
> help to have a look, thanks!
>
>
> $ g++ -Wall* -std=c++11* main_trader.cpp liblog4cplus.a -lpthread
>
> /tmp/ccrHnjIt.o: In function
> `log4cplus::detail::macros_get_logger(log4cplus::Logger&&)':
> main_trader.cpp:(.text._ZN9log4cplus6detail17macros_get_loggerEONS_6LoggerE[_ZN9log4cplus6detail17macros_get_loggerEONS_6LoggerE]+0x2a):
> *undefined reference to `log4cplus::Logger::Logger(log4cplus::Logger&&)*'
> collect2: error: ld returned 1 exit status
>
>
> I use macros like "LOG4CPLUS_ERROR(Logger::getRoot(), p)" in my code.
>
> I'm using Ubuntu13.04, x64.  with g++ 4.7
> $   g++ --version
> g++ (Ubuntu/Linaro 4.7.3-1ubuntu1) 4.7.3
>
>
>
> ----------------------------------------------------------------------------------------------------------------------
> I compiled log4cplus myself, with 'default' option or flags.
>
> (In log4cplus-1.1.2-rc3:)  $ cat ./config.log |grep "c++11"
>
> configure:5755: checking CXXFLAGS for gcc -Wc++11-compat
> configure:5782: g++ -c -g -O2 -Wall -Wextra -pedantic -Wstrict-aliasing
> -Wstrict-overflow -Woverloaded-virtual -Wold-style-cast -Wc++0x-compat
> -pedantic -Werror  -Wc++11-compat  -D_GNU_SOURCE=1 conftest.cpp >&5
> configure:5796: result: -Wc++11-compat
>


-- 
VZ

Re: [Log4cplus-devel] Failed to compile with flag "-std=c++11" in projects

[Delian Xu <del...@gm...>]

If the flag '-std=c++11' is removed, log4cplus and everything goes well.


2013/10/6 Delian Xu <del...@gm...>

> Hello,
>
> How to make log4cplus work with compile-flag "-std=c++11" ?
>
> It seems that log4cplus can work with c++11, but I failed to try it,
> please help to have a look, thanks!
>
>
> $ g++ -Wall* -std=c++11* main_trader.cpp liblog4cplus.a -lpthread
>
> /tmp/ccrHnjIt.o: In function
> `log4cplus::detail::macros_get_logger(log4cplus::Logger&&)':
> main_trader.cpp:(.text._ZN9log4cplus6detail17macros_get_loggerEONS_6LoggerE[_ZN9log4cplus6detail17macros_get_loggerEONS_6LoggerE]+0x2a):
> *undefined reference to `log4cplus::Logger::Logger(log4cplus::Logger&&)*'
> collect2: error: ld returned 1 exit status
>
>
> I use macros like "LOG4CPLUS_ERROR(Logger::getRoot(), p)" in my code.
>
> I'm using Ubuntu13.04, x64.  with g++ 4.7
> $   g++ --version
> g++ (Ubuntu/Linaro 4.7.3-1ubuntu1) 4.7.3
>
>
>
>
> ----------------------------------------------------------------------------------------------------------------------
> I compiled log4cplus myself, with 'default' option or flags.
>
> (In log4cplus-1.1.2-rc3:)  $ cat ./config.log |grep "c++11"
>
> configure:5755: checking CXXFLAGS for gcc -Wc++11-compat
> configure:5782: g++ -c -g -O2 -Wall -Wextra -pedantic -Wstrict-aliasing
> -Wstrict-overflow -Woverloaded-virtual -Wold-style-cast -Wc++0x-compat
> -pedantic -Werror  -Wc++11-compat  -D_GNU_SOURCE=1 conftest.cpp >&5
> configure:5796: result: -Wc++11-compat
>

[Log4cplus-devel] Failed to compile with flag "-std=c++11" in projects

[Delian Xu <del...@gm...>]

Hello,

How to make log4cplus work with compile-flag "-std=c++11" ?

It seems that log4cplus can work with c++11, but I failed to try it, please
help to have a look, thanks!


$ g++ -Wall* -std=c++11* main_trader.cpp liblog4cplus.a -lpthread

/tmp/ccrHnjIt.o: In function
`log4cplus::detail::macros_get_logger(log4cplus::Logger&&)':
main_trader.cpp:(.text._ZN9log4cplus6detail17macros_get_loggerEONS_6LoggerE[_ZN9log4cplus6detail17macros_get_loggerEONS_6LoggerE]+0x2a):
*undefined reference to `log4cplus::Logger::Logger(log4cplus::Logger&&)*'
collect2: error: ld returned 1 exit status


I use macros like "LOG4CPLUS_ERROR(Logger::getRoot(), p)" in my code.

I'm using Ubuntu13.04, x64.  with g++ 4.7
$   g++ --version
g++ (Ubuntu/Linaro 4.7.3-1ubuntu1) 4.7.3



----------------------------------------------------------------------------------------------------------------------
I compiled log4cplus myself, with 'default' option or flags.

(In log4cplus-1.1.2-rc3:)  $ cat ./config.log |grep "c++11"

configure:5755: checking CXXFLAGS for gcc -Wc++11-compat
configure:5782: g++ -c -g -O2 -Wall -Wextra -pedantic -Wstrict-aliasing
-Wstrict-overflow -Woverloaded-virtual -Wold-style-cast -Wc++0x-compat
-pedantic -Werror  -Wc++11-compat  -D_GNU_SOURCE=1 conftest.cpp >&5
configure:5796: result: -Wc++11-compat

[Log4cplus-devel] log4cplus web pages have moved

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

I have moved the content of log4cplus.sourceforge.net
<http://log4cplus.sourceforge.net> web pages to log4cplus's wiki on
SourceForge <http://sourceforge.net/p/log4cplus/wiki/Home/>.

-- 
VZ

[Log4cplus-devel] log4cplus 1.1.2-RC3 released

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

Hi.

I have just released log4cplus 1.1.2-RC3. It contains mainly portability
fixes:

- Fixed build issues on HP-UX with aCC.

- Fixed build issues on Haiku.

- Added mingw-log4cplus.spec to allow cross-compilation from
  Fedora. (John Smits)

- Fixed build issues on AIX with XLC.

- Fixed build issues related to Microsoft's foo_s() functions with
  some version of MinGW tool-chain.

- Tiny speedup of getFormattedTime().

- Imported newer android/android.toolchain.cmake from OpenCV
  repository.

-- 
VZ

Re: [Log4cplus-devel] Socket close hangs

[palladin <p-a...@ya...>]

On 09/19/2013 01:15 AM, Václav Zeman wrote:
> On 09/18/2013 09:51 AM, palladin wrote:
>> Dear log4cplus devels,
>> log4cplus 1.1.1-RC4
>> <https://sourceforge.net/projects/log4cplus/files/log4cplus-stable/1.1.1/>
>> Linux version 2.6.32-279.22.1.37.0.el6.x86_64 (abuild@noriko) (gcc
>> version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) )
>>
>> My application has hung after it have used log4cplus::helpers::Socket
>> from  log4cplus::helpers::ServerSocket::accept,e.g.
>> log4cplus::helpers::Socket clientSocket = mServerSocket.accept();
>> clientSocket was put into log4cplus::thread::AbstractThread worker.
>> Client socket was used in AbstractThread like Socket::read - this is
>> blocking call and the root of issue.
>>
>> Then my application worked for some time  and at the end I did
>> clientSocket.close() from main thread.
>> Due to the fact that log4cplus::helpers::Socket::read is blocking call -
>> my application has hung on AbstractThread::join call.
>>
>> I would like to suggest a fiew fixes to this issue:
>> 1) add non-blocking stuff to log4cplus::helpers::Socket - select or poll.
>> 2) add to log4cplus::helpers::Socket interface system call shutdown( man
>> 2 shutdown ).
> Closing a socket from one thread when the socket is blocked on any
> operation in another thread is AFAIK very unportable.
>
> This could be solved in a way similar to how I have done
> ServerSocket::accept(), which is indeed using poll() to wait for either
> an incoming connection or some data arriving to a special interrupt pipe.
>
> Also, these helpers are there to help log4cplus. They are not there to
> be used as public networking framework/API, so fixing this has a low
> priority for me right now. OTOH, I am open to accepting reasonable patches.
>
>
>
> ------------------------------------------------------------------------------
> LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
> 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
> 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
> Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
> http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> Log4cplus-devel mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4cplus-devel

Dear Václav,
I prefer your solution in ServerSocket interruption. So could you please 
take a look on provided patch?

Sincerely ,
Taras

Re: [Log4cplus-devel] log4cplus WaitForSingleObject pb

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

On 18 September 2013 10:28, Etienne Hovaere wrote:
> Hi,
>
> we're encoutering a problem using log4cplus. I hope you will be able to help
> me. Problem occurs on exiting (log4cplus::Logger::shutdown())  in
> Thread::join() function. It does an infinite WaitForSingleObject ... so the
> app never ends.
> Any idea of what could prevent the thread from been terminated?
Is this the same issue as the one reported recently in log4cplus-devel
ML with sockets?

What is the call stack of all threads? What version of log4cplus are you using?

-- 
VZ

Re: [Log4cplus-devel] Socket close hangs

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

On 09/18/2013 09:51 AM, palladin wrote:
> Dear log4cplus devels,
> log4cplus 1.1.1-RC4
> <https://sourceforge.net/projects/log4cplus/files/log4cplus-stable/1.1.1/>
> Linux version 2.6.32-279.22.1.37.0.el6.x86_64 (abuild@noriko) (gcc
> version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) )
> 
> My application has hung after it have used log4cplus::helpers::Socket
> from  log4cplus::helpers::ServerSocket::accept,e.g.
> log4cplus::helpers::Socket clientSocket = mServerSocket.accept();
> clientSocket was put into log4cplus::thread::AbstractThread worker.
> Client socket was used in AbstractThread like Socket::read - this is
> blocking call and the root of issue.
> 
> Then my application worked for some time  and at the end I did
> clientSocket.close() from main thread.
> Due to the fact that log4cplus::helpers::Socket::read is blocking call -
> my application has hung on AbstractThread::join call.
> 
> I would like to suggest a fiew fixes to this issue:
> 1) add non-blocking stuff to log4cplus::helpers::Socket - select or poll.
> 2) add to log4cplus::helpers::Socket interface system call shutdown( man
> 2 shutdown ).
Closing a socket from one thread when the socket is blocked on any
operation in another thread is AFAIK very unportable.

This could be solved in a way similar to how I have done
ServerSocket::accept(), which is indeed using poll() to wait for either
an incoming connection or some data arriving to a special interrupt pipe.

Also, these helpers are there to help log4cplus. They are not there to
be used as public networking framework/API, so fixing this has a low
priority for me right now. OTOH, I am open to accepting reasonable patches.

-- 
VZ

[Log4cplus-devel] Socket close hangs

[palladin <p-a...@ya...>]

Dear log4cplus devels,
log4cplus 1.1.1-RC4 
<https://sourceforge.net/projects/log4cplus/files/log4cplus-stable/1.1.1/>
Linux version 2.6.32-279.22.1.37.0.el6.x86_64 (abuild@noriko) (gcc 
version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) )

My application has hung after it have used log4cplus::helpers::Socket 
from log4cplus::helpers::ServerSocket::accept,e.g.
log4cplus::helpers::Socket clientSocket = mServerSocket.accept();
clientSocket was put into log4cplus::thread::AbstractThread worker. 
Client socket was used in AbstractThread like Socket::read - this is 
blocking call and the root of issue.

Then my application worked for some time  and at the end I did 
clientSocket.close() from main thread.
Due to the fact that log4cplus::helpers::Socket::read is blocking call - 
my application has hung on AbstractThread::join call.

I would like to suggest a fiew fixes to this issue:
1) add non-blocking stuff to log4cplus::helpers::Socket - select or poll.
2) add to log4cplus::helpers::Socket interface system call shutdown( man 
2 shutdown ).

Sincerely,
Taras Shypytiak.

Re: [Log4cplus-devel] Logging QT Objects using Log4cplus

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

On 09/05/2013 04:42 PM, Umesh Sharma wrote:
> Hi ,
> I am wondering if log4cplus supports  logging of QT object.
> e.g. LOG4CPLUS_INFO(loggerId,   QStringobj)   or 
>       LOG4CPLUS_INFO(loggerId,   QMapobj)
> 
> It is giving compilation error that 
> Generally when we use qdebug(), we just have to write following statement :-
> 
> qdebug() << QStringObj;
> qdebug() << QmapObj;
> 
> 
> Let me know if you have any solution with regards to that.

I do not think that this is possible with log4cplus without me actually
writing a lot of operator<< implementations.

-- 
VZ

Re: [Log4cplus-devel] [log4cplus] Getting filname and path of RollingFileAppender

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

On 08/20/2013 04:59 PM, Harald Pauli wrote:
> Hi,
>  
> first of all, many thanks for log4cplus. It is a good platform for logging.
> My problem is that I need to get the complete path to the log file that
> is written by a RollingFileAppender and the only key I have is the
> logger name. I already found the way to the appender via getInstance()
> and getAppender() but I'm stuck there.
>  
> Is there a way to solve this issue?
At this point there is no way to retrieve the file name. This would have
to be solved by adding some, e.g., getFilename(), accessor to the
FileAppender class. In any case, there will be no path normalization,
what the class receives in ctor or in properties that will be stored in
FileAppender::filename member variable. Feel free to send a patch
implementing such FileAppender::getFilename() function.

-- 
VZ

Re: [Log4cplus-devel] Failed to compile using cmake android toolchain

[Nikita M. <nik...@gm...>]

Hi,

I will look at the problem this week. Probably I will find a solution and
send a patch if it is necessary.


2013/8/14 Václav Zeman <vha...@gm...>

> On 14 August 2013 11:58, Vladimir "Equidamoid" Shapranov wrote:
> > It seems that the error is caused by -fdata-sections flag set by
> > android.toolchain.cmake (line 930).
> > I don't actually understand why that flag is needed there but addng
> >
> > if (ANDROID)
> >
> >     add_definitions(-fno-data-sections)
> >
> > endif(ANDROID)
> >
> >
> > to log4cplus/src/CMakeLists.txt fixes the issue.
> I am glad that you found a work around for this issue.
>
> I have updated the android.toolchain.cmake file from the OpenCV
> repository at <
> http://code.opencv.org/projects/opencv/repository/revisions/master/changes/platforms/android/android.toolchain.cmake
> >.
> However the updated file still contains the offending -fdata-sections
> flag. I think that we (I actually mean you :) should do two things:
>
> 1. document the issue and your workaround in README;
> 2. complain to Google (fill a bug report) that their NDK
> compiler/toolchain does not properly support thread local storage.
>
> >
> > 13.08.2013 21:35 , Václav Zeman пишет:
> >
> > On 08/12/2013 07:13 PM, Vladimir "Equidamoid" Shapranov wrote:
> >
> > Hello,
> >
> > I'm trying to build log4cplus for android using cmake (added
> > 'add_subdirectory(path/to/the/source)' to my main CMakeLists.txt).
> > The build crashes with the following error:
> > [ 48%] Building CXX object
> > jni/lib/log4cplus-1.1.1/src/CMakeFiles/log4cplus.dir/global-init.cxx.o
> > jni/lib/log4cplus-1.1.1/src/global-init.cxx:268:46: error:
> > log4cplus::internal::__emutls_t._ZN9log4cplus8internal3ptdE causes a
> > section type conflict with log4cplus::internal::ptd
> > jni/lib/log4cplus-1.1.1/src/global-init.cxx:268:46: note:
> > 'log4cplus::internal::ptd' was declared here
> >
> > Is this a bug or I'm doing something wrong?
> >
> > This looks like a deficiency in the Android tool chain. The only problem
> > with log4cplus is probably that its CMake scripts do not detect that the
> > tool chain is lacking this feature.
> >
> > I am adding Nikita Manovich to CC because he is the one who has
> > contributed the Android port patches.
>
> --
> VZ
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> _______________________________________________
> Log4cplus-devel mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4cplus-devel
>



-- 
  Best regards,
    Nikita Manovich.

Re: [Log4cplus-devel] Failed to compile using cmake android toolchain

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

On 14 August 2013 11:58, Vladimir "Equidamoid" Shapranov wrote:
> It seems that the error is caused by -fdata-sections flag set by
> android.toolchain.cmake (line 930).
> I don't actually understand why that flag is needed there but addng
>
> if (ANDROID)
>
>     add_definitions(-fno-data-sections)
>
> endif(ANDROID)
>
>
> to log4cplus/src/CMakeLists.txt fixes the issue.
I am glad that you found a work around for this issue.

I have updated the android.toolchain.cmake file from the OpenCV
repository at <http://code.opencv.org/projects/opencv/repository/revisions/master/changes/platforms/android/android.toolchain.cmake>.
However the updated file still contains the offending -fdata-sections
flag. I think that we (I actually mean you :) should do two things:

1. document the issue and your workaround in README;
2. complain to Google (fill a bug report) that their NDK
compiler/toolchain does not properly support thread local storage.

>
> 13.08.2013 21:35 , Václav Zeman пишет:
>
> On 08/12/2013 07:13 PM, Vladimir "Equidamoid" Shapranov wrote:
>
> Hello,
>
> I'm trying to build log4cplus for android using cmake (added
> 'add_subdirectory(path/to/the/source)' to my main CMakeLists.txt).
> The build crashes with the following error:
> [ 48%] Building CXX object
> jni/lib/log4cplus-1.1.1/src/CMakeFiles/log4cplus.dir/global-init.cxx.o
> jni/lib/log4cplus-1.1.1/src/global-init.cxx:268:46: error:
> log4cplus::internal::__emutls_t._ZN9log4cplus8internal3ptdE causes a
> section type conflict with log4cplus::internal::ptd
> jni/lib/log4cplus-1.1.1/src/global-init.cxx:268:46: note:
> 'log4cplus::internal::ptd' was declared here
>
> Is this a bug or I'm doing something wrong?
>
> This looks like a deficiency in the Android tool chain. The only problem
> with log4cplus is probably that its CMake scripts do not detect that the
> tool chain is lacking this feature.
>
> I am adding Nikita Manovich to CC because he is the one who has
> contributed the Android port patches.

-- 
VZ

Re: [Log4cplus-devel] Failed to compile using cmake android toolchain

[Vladimir \Equidamoid\ S. <equ...@gm...>]

It seems that the error is caused by -fdata-sections flag set by 
android.toolchain.cmake (line 930).
I don't actually understand why that flag is needed there but addng


if (ANDROID)

     add_definitions(-fno-data-sections)

endif(ANDROID)


to log4cplus/src/CMakeLists.txt fixes the issue.

13.08.2013 21:35 , Václav Zeman ?????:
> On 08/12/2013 07:13 PM, Vladimir "Equidamoid" Shapranov wrote:
>> Hello,
>>
>> I'm trying to build log4cplus for android using cmake (added
>> 'add_subdirectory(path/to/the/source)' to my main CMakeLists.txt).
>> The build crashes with the following error:
>> [ 48%] Building CXX object
>> jni/lib/log4cplus-1.1.1/src/CMakeFiles/log4cplus.dir/global-init.cxx.o
>> jni/lib/log4cplus-1.1.1/src/global-init.cxx:268:46: error:
>> log4cplus::internal::__emutls_t._ZN9log4cplus8internal3ptdE causes a
>> section type conflict with log4cplus::internal::ptd
>> jni/lib/log4cplus-1.1.1/src/global-init.cxx:268:46: note:
>> 'log4cplus::internal::ptd' was declared here
>>
>> Is this a bug or I'm doing something wrong?
> This looks like a deficiency in the Android tool chain. The only problem
> with log4cplus is probably that its CMake scripts do not detect that the
> tool chain is lacking this feature.
>
> I am adding Nikita Manovich to CC because he is the one who has
> contributed the Android port patches.
>
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> Log4cplus-devel mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4cplus-devel


-- 
Best regards,
Vladimir

Re: [Log4cplus-devel] Failed to compile using cmake android toolchain

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

On 08/12/2013 07:13 PM, Vladimir "Equidamoid" Shapranov wrote:
> Hello,
> 
> I'm trying to build log4cplus for android using cmake (added 
> 'add_subdirectory(path/to/the/source)' to my main CMakeLists.txt).
> The build crashes with the following error:
> [ 48%] Building CXX object 
> jni/lib/log4cplus-1.1.1/src/CMakeFiles/log4cplus.dir/global-init.cxx.o
> jni/lib/log4cplus-1.1.1/src/global-init.cxx:268:46: error: 
> log4cplus::internal::__emutls_t._ZN9log4cplus8internal3ptdE causes a 
> section type conflict with log4cplus::internal::ptd
> jni/lib/log4cplus-1.1.1/src/global-init.cxx:268:46: note: 
> 'log4cplus::internal::ptd' was declared here
> 
> Is this a bug or I'm doing something wrong?
This looks like a deficiency in the Android tool chain. The only problem
with log4cplus is probably that its CMake scripts do not detect that the
tool chain is lacking this feature.

I am adding Nikita Manovich to CC because he is the one who has
contributed the Android port patches.

-- 
VZ