Vitaly wrote:
>>So your xercesc library doesn't contain SocketNetAccessor after compiling.
>>But another library with SocketNetAccessor
>>implementation has been used by your program in runtime.
>>May be the problem is in this linker option (look at two different xercesc
>>folders):
>>-Wl,/net/sinai/home/d/dcd9420/labs/xercesLab/xerces-c-3.0.1/src/.libs:/site/sw/ots/curl/curl-7.19.6/lib:/site/ots/xerces/xerces-c-3.0.1/lib
====================================================================
I taken a look at some of the Makefiles generated by the configure script. I
specified the following options to
Configure:
./configure --prefix=/site/sw/ots/xerces/xerces-c-3.0.1
--exec-prefix=/site/ots/xerces/xerces-c-3.0.1 CXX=/opt/aCC/bin/aCC
CXXFLAGS="-Aa -mt -g" CPPFLAGS="-I/site/sw/ots/curl/curl-7.19.6/include"
--enable-netaccessor-curl --with-curl=/site/sw/ots/curl/curl-7.19.6
Since I did not specify the LDFLAGS options, the configure script generated the
linker options. It used the --exec-prefix for the
/site/sw/ots/xerces/xerces-c-3.0.1/lib path and the --with-curl to generate
/site/sw/ots/curl/curl-7.19.6/lib. I don't know why the script added the path
/net/sinai/home/d/dcd9420/labs/xercesLab/xerces-c-3.0.1/src/.libs to the -Wl
linker option or why it generated this particular option. Should I set the
LDFLAGS and if so to what?
