On Jun 19, 2008, at 4:27 AM, Katharina Maurer wrote:


Hi, everybody!


I want to build log4cxx-0-10.0.

I have:
- MinGW-5.1.3.
- Msys-1.0.10.
- msysDTK-1.0.1.
- Python-2.5.1.
- apr (apr_20080408042052)
- apr-util (apr-util_20080408042135)
- expat-2.0.1.
- cppunit-1.12.1.


I have no problems with building apr, apr-util, expat and cppunit.

I use following code:

autogen.sh
pwd
./configure --with-apr=../apr --with-apr-util=../apr-util --with- cppunit=../cppunit-1.12.1 --with-expat=../expat-2.0.1 --with- logchar=wchar_t
make
make install


And I get this error:

threadcxx.cpp: In member function `void log4cxx::helpers::Thread::run(void*(*)(apr_thread_t*, void*), void*)': threadcxx.cpp:76: error: invalid conversion from `void*(*) (apr_thread_t*, void*)' to `void*(*)(apr_thread_t*, void*)' threadcxx.cpp:76: error: initializing argument 3 of `apr_status_t apr_thread_create(apr_thread_t**, apr_threadattr_t*, void*(*) (apr_thread_t*, void*), void*, apr_pool_t*)'
make[3]: *** [threadcxx.lo] Error 1
make[3]: Leaving directory `/d/soft/apache-log4cxx-0.10.0/src/main/ cpp'
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory `/d/soft/apache-log4cxx-0.10.0/src/main'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/d/soft/apache-log4cxx-0.10.0/src'
make: *** [install-recursive] Error 1


Please, can anybody help me. Thank you in advance!!!!

Katharina Maurer

log4cxx no longer depends on cppunit and the expat dependency should be indirectly through apr-util, so you could likely drop building and --within those.

I haven't seen this before, but it is possible that a slight difference between the forward declaration of apr_thread_t in src/main/ include/log4cxx/helpers/thread.h and the definition in ../apr/include/ apr_thread_proc.h might be resulting in having two slightly different versions ofapr_thread_t* in scope. Or possibly the calling convention (LOG4CXX_THREAD_FUNC in log4cxx/thread.h) is slightly different than in the APR header.

Don't have that MinGW environment handy, so can't give you a quick workaround.

Reply via email to