David,

I had a problem in the "ld" version, and a missing compilation flag (-fPIC).

I fixed it, and now it works.

Thanks.

Nunzio Palmentieri
Web Care Solution
 
Engineering.IT S.p.A.
Via Antiniana 2/a 
80078 Pozzuoli (NA) - ITALY
 
Direct        +39 081 6103 388
Mobile       +39 335 1214 806
Fax             +39 081 6103 200
e-mail        mailto:[email protected]
Web            http://www.eng.it/
This electronic message contains information from Engineering.IT, which may
be privileged and confidential. The information is intended to be use of the
individual(s) or entity named above. If you are not the intended recipient,
be aware that any disclosure, copying, distribution or use of the contents
of this information is prohibited.

-----Messaggio originale-----
Da: David Bertoni [mailto:[email protected]] 
Inviato: mercoledì 15 aprile 2009 20.26
A: [email protected]
Oggetto: Re: Ldd problem on library linking libxerces-c.so.28.0

Palmentieri Nunzio wrote:
> Hi all,
> I have the following problem when I perform ldd -d on a library that 
> links libxerces-c.so.28.0
>  
>         libsocket.so.1 =>        /usr/lib/libsocket.so.1
>         libnsl.so.1 =>   /usr/lib/libnsl.so.1
>         libxerces-c.so.28 =>     
>
/PFEapp/PFEdev/DEV_PLAT_NAT_1.0/BE/PFE/third_parts/Xerces/xerces-dev-usage-2
_8_0/lib/libxerces-c.so.28
>         libxerces-depdom.so.28 =>        
>
/PFEapp/PFEdev/DEV_PLAT_NAT_1.0/BE/PFE/third_parts/Xerces/xerces-dev-usage-2
_8_0/lib/libxerces-depdom.so.28
>         libxalanMsg.so.110 =>    
>
/PFEapp/PFEdev/DEV_PLAT_NAT_1.0/BE/PFE/third_parts/Xalan/xml-xalan-dev-usage
/lib/libxalanMsg.so.110
>         libxalan-c.so =>         
>
/PFEapp/PFEdev/DEV_PLAT_NAT_1.0/BE/PFE/third_parts/Xalan/xml-xalan-dev-usage
/lib/libxalan-c.so
>         libc.so.1 =>     /usr/lib/libc.so.1
>         libmp.so.2 =>    /usr/lib/libmp.so.2
>         libmd5.so.1 =>   /usr/lib/libmd5.so.1
>         libscf.so.1 =>   /usr/lib/libscf.so.1
>         libpthread.so.1 =>       /usr/lib/libpthread.so.1
>         libgen.so.1 =>   /usr/lib/libgen.so.1
>         libstdc++.so.6 =>        /usr/sfw/lib/libstdc++.so.6
>         libm.so.2 =>     /usr/lib/libm.so.2
>         libgcc_s.so.1 =>         /usr/sfw/lib/libgcc_s.so.1
>         libdoor.so.1 =>  /usr/lib/libdoor.so.1
>         libuutil.so.1 =>         /usr/lib/libuutil.so.1
>         symbol not found: 
> __1cLxercesc_2_8GXMLUniWfgXercescDefaultLocale_               
> (./libXalanC.so)
>         symbol not found: 
> __1cLxercesc_2_8QXMLPlatformUtilsPfgMemoryManager_            
> (./libXalanC.so)

You apparently have a library called libXalanC.so linked in, which is
another Xalan-C library with a non-default name.  Are you doing this on
purpose?  What is the nature of this library?

This is an issue with either Xalan-C, or with your application, so please
consider following up on the Xalan-C user list, and not on the Xerces-C
developer list.

Dave

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to