I have also had this problem. I think that the procedure for newbies really
needs to be clarified. I skipped building the samples, and only figured out
the gcc options for Xerces because I asked someone on the mailing list. I'm
not in linux right now, so I don't remember them now.

Sarah

-----Original Message-----
From: Widi Sagita [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 20, 2002 4:45 AM
To: [EMAIL PROTECTED]
Subject: Re: Clarification needed on DOM memory management


hello all,
i'm really newbie in xerces

i've already install xerces 2.1.0 and i think it's work
but when i try to build the samples directory, error occured..

for information, i use SCO OpenServer 5.0.6
gcc ver 2.95.2
installation configuration:
runConfigure -popenserver -cgcc -xg++ -rnone -nsocket
configuration step seemed OK, then i make.. no problem..

build sample directory error:

Undefined                       first referenced
 symbol                             in file
XMLPlatformUtils::openFileToWrite(unsigned short const
*)/ext1/home/widi/xerces-c-src2_1_0/lib/libxerces-c.so
XMLPlatformUtils::writeBufferToFile(void *, long, unsigned char const
*)/ext1/home/widi/xerces-c-src2_1_0/lib/libxerces-c.so
XMLPlatformUtils::openFileToWrite(char const
*)/ext1/home/widi/xerces-c-src2_1_0/lib/libxerces-c.so
/ext1/home/widi/xerces-c-src2_1_0/bin/SAXPrint: fatal error: Symbol
referencing errors. No output written to
/ext1/home/widi/xerces-c-src2_1_0/bin/SAXPrint

collect2: ld returned 1 exit status
make[1]: *** [/ext1/home/widi/xerces-c-src2_1_0/bin/SAXPrint] Error 1
make[1]: Leaving directory
`/ext1/home/widi/xerces-c-src2_1_0/samples/SAXPrint'
make: *** [saxprint] Error 2

anyone can help solving this problem?

thanks,
..widi

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to