Arundhati,

Thanks for the suggestions.  Here is what I found.

I was using the /opt/gnu/bin/make.  I saw some g++ internal compiler errors
once -O 
flags is on.  The same result when I tried compiling again on different
boxes.
So for now I just compile with -g and strip off the symbols afterwards.


James

-----Original Message-----
From: Arundhati Bhowmick [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 01, 2000 10:37 AM
To: [EMAIL PROTECTED]
Subject: Re: Compiling libxerces-c1_0.so


James,
Only difference I see is you using 'make' to build the source and samples.
Use
'gmake' instead. Besides when you build the source try to output in a log
file
and see if there are any errors in the building process. I feel somewhere in
the
dom compilation its breaking. The library doen't stop even if there are
errors
in compilation. So, you get the undefined symbols on compilation of samples.
I
again tried doing it on my machine but cannot reproduce your problem here.

Arundhati

"Ching, James" wrote:

> Arundhati,
>
> Thanks for the response.  Attached is the error messages.
>
> James
>
> -----Original Message-----
> From: Arundhati Bhowmick [mailto:[EMAIL PROTECTED]
> Sent: Monday, January 31, 2000 1:01 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Compiling libxerces-c1_0.so
>
> James,
> I'm not sure why you're getting those linking errors. We over here also
use
> solaris 2.6 with gcc 2.8.1. And I've been compiling most of the time with
> out
> -d option but don't get any linking problems.
> Did you have you LD_LIBRARY_PATH set to the right directories of system
> libraries?
> What were the linking errors? Can you paste them up here?
>
> Arundhati
>
> "Ching, James" wrote:
>
> > I downloaded Xerces-C-src_1_0_1 (XML parser for C++) and compiled it on
> > Solaris 2.6 with gcc 2.8.1.
> >
> > I can successfully link the resulting shared library with the debug flag
> > turned on
> > % runConfigure -p solaris -c gcc -x g++ -d
> >
> > Yet once I remove the "-d" flag, I got a list of linking errors on
symbols
> > referenced
> > not found.  Does anyone had the similar problem?
> >
> > Any suggestion is greatly appreciated!
> >
> > James
>
>   ------------------------------------------------------------------------
>                   Name: Compile.txt
>    Compile.txt    Type: Plain Text (text/plain)
>               Encoding: quoted-printable

Reply via email to