You would need to give us the following information:

What is the configure command that you gave for apr, aprutil, and log4cxx,
and all other related dependencies? 


By the symptom it looks like you did not do a "make install" on the
dependencies and hence your app is trying to link to something that libtool
generates temporarily (.la). I maybe wrong. But please do a "make install"
on all ur dependencies.

Try to build everything from scratch one more time and the wiki page to do
that is here:
http://wiki.apache.org/logging-log4cxx/MSWindowsBuildInstructions

Thanks
L.K




Katharina Maurer wrote:
> 
> 
> Thank you very much for your support!!! 
> 
> I changed the lines and now it is working till the end. But now I have
> other question. Maybe you can help me again. I have to say that  am very
> unexperienced with log4cxx and deeply grateful for all suggestions..
> 
> I'm worry about following messages I get twice:
> 
> *** Warning: This system can not link to static lib archive
> /d/soft/apr-util/libaprutil-1.la.
> *** I have the capability to make that library automatically link in when
> *** you link to this library.  But I can only do this if you have a
> *** shared version of the library, which you do not appear to have.
> 
> *** Warning: This system can not link to static lib archive
> /d/soft/apr/libapr-1.la.
> *** I have the capability to make that library automatically link in when
> *** you link to this library.  But I can only do this if you have a
> *** shared version of the library, which you do not appear to have
> 
> Do I have to change the apr and apr-util installation or configure options
> for log4cxx configuration?
> 
> Thanks a lot again and have a good weekend!
> 
> Katharina
> 
> 
> -------- Original-Nachricht --------
>> Datum: Wed, 2 Jul 2008 09:37:43 -0700 (PDT)
>> Von: lakshmikanth <[EMAIL PROTECTED]>
>> An: log4cxx-user@logging.apache.org
>> Betreff: Re: problems with building log4cxx-0-10.0. in threadcxx.cpp
> 
>> 
>> 
>> Curt Arnold-3 wrote:
>> > 
>> > 
>> > 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.
>> > 
>> > 
>> 
>> The above is the reason why its happening, quick and dirty work around is 
>> to remove the following set of lines from thread.h, that will get you
>> going:
>> 
>> #if !defined(LOG4CXX_THREAD_FUNC)
>> #if defined(_WIN32)
>> #define LOG4CXX_THREAD_FUNC __stdcall
>> #else
>> #define LOG4CXX_THREAD_FUNC
>> #endif
>> #endif
>> 
>> 
>> and add this instead:
>> 
>> #if !defined(LOG4CXX_THREAD_FUNC)
>> #define LOG4CXX_THREAD_FUNC
>> #endif
>> 
>> 
>> P.S: Sorry, no time to mess around with diff :)
>> 
>> -- 
>> View this message in context:
>> http://www.nabble.com/problems-with-building-log4cxx-0-10.0.-in-threadcxx.cpp-tp18000912p18241817.html
>> Sent from the Log4cxx - Users mailing list archive at Nabble.com.
> 
> -- 
> Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! 
> Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
> 
> 

-- 
View this message in context: 
http://www.nabble.com/problems-with-building-log4cxx-0-10.0.-in-threadcxx.cpp-tp18000912p18284786.html
Sent from the Log4cxx - Users mailing list archive at Nabble.com.

Reply via email to