logging-log4cxx-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Madan, Hatinder" <hatinder.ma...@gs.com>
Subject Problems using log4cxx built on Solaris 8!
Date Fri, 05 Nov 2004 13:12:39 GMT
Hello everybody,
 I have compiled the log4cxx and built the shared library on Solaris 8
While I link this library dynamically to build my executable, I see the
following error:
Undefined                       first referenced
 symbol                             in file
long __rwstd::InterlockedDecrement(long*)
long __rwstd::InterlockedIncrement(long*)
long __rwstd::InterlockedExchange(long*,long)
ld: fatal: Symbol referencing errors. No output written

The following is the output of nm -o -C liblogcxx.so | grep Interlocked
[14131] |000000000000|000000000000|NOTY |GLOB |0    |UNDEF  |long
[13326] |000000000000|000000000000|NOTY |GLOB |0    |UNDEF  |long
[15089] |000000000000|000000000000|NOTY |GLOB |0    |UNDEF  |long
[14430] |000007275110|000000000140|FUNC |GLOB |0    |11     |long
log4cxx::helpers::Thread::InterlockedDecrement(volatile lon\
[14672] |000007274730|000000000140|FUNC |GLOB |0    |11     |long
log4cxx::helpers::Thread::InterlockedIncrement(volatile lon\

1) How is the scope for the undefined symbols being resolved to __rwstd:: ??
2) Another thing I notice is that these functions (Interlocked*) occur only
in 3 source files: condition.cpp, thread.cpp, objectimpl.cpp.
    The references in the last file objectimpl.cpp are to the functions
Thread::Interlocked*. Hence, these are being resolved.
    In the other 2 files, condition.cpp thread.cpp, whatever references
exist (barring the definition of the member version of Thread class), they
    been EXCLUDED out by the pre-processor (controlled by pre-processor
macros like HAVE_MS_THREAD) !!! I have duly defined the macro 

I would greatly appreciate your suggestions/ ideas on how to resolve this.


View raw message