|
The output you should get must look similar
to:
Shared
Library Load List for CreateDOMDocument:
Order Name
0
CreateDOMDocument
1 ^
/usr/lib/libpthread.1
2 ^
/home/egarciam/desllo/xerces/xerces-c-src_2_3_0/lib/libxerces-c.sl.23
(don't mind about the path)
3
^ ^ /usr/lib/libpthread.1
4
^ ^ /usr/lib/libnsl.1
5
^ ^ ^ /usr/lib/libxti.2
6 ^ /usr/lib/libstd_v2.2
7 ^ /usr/lib/libCsup_v2.2
8 ^ /usr/lib/libm.2
9 ^ /usr/lib/libcl.2
10 ^ ^ /usr/lib/libdld.2
11 ^ ^ /usr/lib/libisamstub.1
12 ^ /usr/lib/libc.2
13 ^ ^ /usr/lib/libdld.2
14 ^ /usr/lib/libdld.2
You
are missing libstd_v2.2 which is where the missing symbols are
defined.
I
think the easiest way to solve this is to rebuild your samples using the
runConfigure script, located in $XERCESCROOT/samples.
The
following command line will do
runConfigure -p hp-11 -x aCC -c cc -r pthread -b
32 -z -AA (assuming you have installed the
support runtime for this option - an HP aCC patch) but I guess you must because
you have already built the library itself. Afterwards move into the source
directory and build the files after cleaning(with gmake, because HP make
complains)
The -r option in runConfigure depends in your threading
options. Usually the best way to avoid such problems is to build the xerces lib
and samples withe the same options.
I hope
this helps
Regards
Ernesto
hi,
Thank you
very much for your suggestion. Here is the output after executing
command, $odump -sllibloadlist
CreateDOMDocument
Output:
$
odump -sllibloadlist CreateDOMDocument
Shared Library Load List for
CreateDOMDocument:
Order Name
0
CreateDOMDocument
1 ^
/usr/lib/libpthread.1
2 ^
/usr/lib/libxerces-c.sl.23
3
^ ^ /usr/lib/libpthread.1
4 ^ ^ /usr/lib/libnsl.1
5 ^ ^ ^
/usr/lib/libxti.2
6 ^
/usr/lib/libstd.2
7 ^
/usr/lib/libstream.2
8 ^
/usr/lib/libCsup.2
9 ^
/usr/lib/libm.2
10 ^
/usr/lib/libcl.2
11 ^ ^
/usr/lib/libdld.2
12 ^ ^
/usr/lib/libisamstub.1
13 ^
/usr/lib/libc.2
14 ^ ^
/usr/lib/libdld.2
15 ^
/usr/lib/libdld.2
I gave the aCC option while building the sample files. I am new to
unix, so could you please analyse the above output and give me the
solution.
Thanks a lot.
-Kathir.V
----- Original Message -----
Sent: Friday, December 05, 2003 4:21
PM
Subject: RE: Unresolved error while
running samples in xerces (HP-UX 11)
Hi,
change dir to $XERCESCROOT/bin (assumming the
samples are created there)
could you post the output from the following
program?
$odump -sllibloadlist CreateDOMDocument
Probably you are missing the "-AA" aCC flag when building your
sample files. This is just a guess. The odump output will tell the lib
dependencies of the exec file
Regards
Hi all,
I have buid
the "xerces-c 2.3.0" in HP-Unix-11 platform for 32 bit and also
build the samples in the bin directory.
But when i
run any of scripts in bin directory like:
CreateDOMDocument
EnumVal
Redirect
SAXCount
StdInParse
DOMCount
MemParse
SAX2Count
SAXPrint
core
DOMPrint
PParse
SAX2Print
SEnumVal
obj
I got following unresolved symbol error:
$
./SAX2Count
/usr/lib/dld.sl: Unresolved symbol:
[Vtable]key:__dt__Q2_3std9exceptionFv (data) from
/usr/lib/libxerces-c.sl.23
/usr/lib/dld.sl: Unresolved symbol:
__nullref__Q2_3std12basic_stringXTcTQ2_3std11char_traitsXTc_TQ2_3std9allocatorXTc__
(data) from /usr/lib/libxerces-c.sl.23
/usr/lib/dld.sl:
Unresolved symbol: cout__3std (data) from
/usr/lib/libxerces-c.sl.23
/usr/lib/dld.sl: Unresolved symbol:
_C_sync_with_stdio__Q2_3std8ios_base (data) from
/usr/lib/libxerces-c.sl.23
/usr/lib/dld.sl: Unresolved symbol:
__rw_std_streams__3std (data) from
/usr/lib/libxerces-c.sl.23
/usr/lib/dld.sl: Unresolved symbol:
typeid__XTQ2_3std9exception_ (data) from
/usr/lib/libxerces-c.sl.23
/usr/lib/dld.sl: Unresolved symbol:
_C_classic_table__Q2_3std5ctypeXTc_ (data) from
/usr/lib/libxerces-c.sl.23
Abort(coredump)
Can any one provide me a solution?????
Thanks & Regards,
Kathiravan.V
_____________________________________________________________
Uni2 Telecomunicaciones, S.A.U.
Aviso legal:
Este mensaje electr�nico est� dirigido
�nicamente a la(s) direcci�n(es) indicadas anteriormente; el car�cter
confidencial, personal e intransferible del mismo est� protegido legalmente.
Cualquier revelaci�n, uso o reenv�o no autorizado, completo o en parte, est�
prohibido.
Si ha recibido este mensaje por equivocaci�n,
notif�quelo inmediatamente a la persona que lo ha enviado y borre el mensaje
original junto con sus ficheros anexos sin leerlo ni grabarlo, total o
parcialmente.
Gracias
_____________________________________________________________
Uni2 Telecomunicaciones, S.A.U.
Aviso legal:
Este mensaje electr�nico est� dirigido �nicamente a la(s) direcci�n(es) indicadas anteriormente; el car�cter confidencial, personal e intransferible del mismo est� protegido legalmente. Cualquier revelaci�n, uso o reenv�o no autorizado, completo o en parte, est� prohibido.
Si ha recibido este mensaje por equivocaci�n, notif�quelo inmediatamente a la persona que lo ha enviado y borre el mensaje original junto con sus ficheros anexos sin leerlo ni grabarlo, total o parcialmente.
Gracias
| 