Simpler Navigation for Servers and Operating Systems
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
cancel
Showing results for 
Search instead for 
Did you mean: 

"Unresolved symbols" error

Highlighted
Bharath K
Occasional Advisor

"Unresolved symbols" error

Dear all,
I am getting the following "Unresolved symbols" error when I try to run the executable which has been built with aCC 3.60 on HP-UX 11.11.Also I have used -AA option when building my executable.libmaverick50 & libxerces-c2_1 are third party libraries which has been built on a aCC 3.13.
Can any one tell me if there is any link option or library to be included to solve this problem?
********** LOG *************************
/usr/lib/dld.sl: Unresolved symbol: cout (data) from /home/builder/tibco/tra/5.2/lib/libmaverick50.sl
/usr/lib/dld.sl: Unresolved symbol: openprot__7filebuf (data) from /home/builder/tibco/tar/5.2/lib/libmaverick50.s
l
/usr/lib/dld.sl: Unresolved symbol: cout (data) from /home/builder/tibco/tpcl/5.2/lib/libxerces-c2_1.sl
/usr/lib/dld.sl: Unresolved symbol: cerr (data) from /home/builder/tibco/tra/5.2/lib/libmaverick50.sl
/usr/lib/dld.sl: Unresolved symbol: basefield__3ios (data) from /home/builder/tibco/5.2/lib/libmaverick50.sl
Abort(coredump)
**********End of Log************************
14 REPLIES
Muthukumar_5
Honored Contributor

Re: "Unresolved symbols" error

Try to export SHLIB_PATH=/usr/lib and run the executable.

hth.
Easy to suggest when don't know about the problem!
Vibhor Kumar Agarwal
Esteemed Contributor

Re: "Unresolved symbols" error

And to

/home/builder/tibco/tpcl/5.2/lib
Vibhor Kumar Agarwal
Bharath K
Occasional Advisor

Re: "Unresolved symbols" error

Thanks Muthu and Agarwal for your immediate response.
The shlib path has been updated to point to /usr/lib and /home/builder/tibco/tpcl/5.2/lib
and other required libraries.
I am still facing the same errors.
regards,
-Bharath
Stephen Keane
Honored Contributor

Re: "Unresolved symbols" error

What happens if you run ldd against your executable?

# ldd your_exe

Muthukumar_5
Honored Contributor

Re: "Unresolved symbols" error

Check this,

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=727237

Do you have patch PHS_22898 installed?

hth.
Easy to suggest when don't know about the problem!
Vibhor Kumar Agarwal
Esteemed Contributor

Re: "Unresolved symbols" error

If your system is 64 bit then i think you have to update your

LD_LIBRARY_PATH
Vibhor Kumar Agarwal
Bharath K
Occasional Advisor

Re: "Unresolved symbols" error

Hi Stephan,
On running ldd , I am able to see the list of all the libraries referred and their paths.The ldd is able to find the all the required libraries.

Thanks,
Bharath
Stephen Keane
Honored Contributor

Re: "Unresolved symbols" error

If ldd works OK, then your SHLIB_PATH is probably setup correctly. Do you have (in /usr/lib) libstream.sl, libC.sl, libC.ansi.sl ?
Vibhor Kumar Agarwal
Esteemed Contributor

Re: "Unresolved symbols" error

Cross-Check the patches on which the third party libraries had been built.
Vibhor Kumar Agarwal
Bharath K
Occasional Advisor

Re: "Unresolved symbols" error

Hi Muthukumar,
The latest patch applied is PHSS_31221.
I think this will cover the patch PHS_22898 also.
-Bharath
Bharath K
Occasional Advisor

Re: "Unresolved symbols" error

Hi Stephen,
The /usr/lib has all of the following libraries
libstream.sl, libC.sl, libC.ansi.sl.
-Bharath
Bharath K
Occasional Advisor

Re: "Unresolved symbols" error

Hi Vibhor Agarwal,
I will try to know on what patches the third party libraries have been built.I dont know from which library these unresolved symbols come from.
-Bharath
Stephen Keane
Honored Contributor

Re: "Unresolved symbols" error

Have you used

using namespace std;

in your source code?
Bharath K
Occasional Advisor

Re: "Unresolved symbols" error

Stephen,
I have'nt used the using name space std.
But the aCC 3.60 compiler automatically does that.
This warning which I got when I compiled my code suggests that:

Warning 890: "/opt/aCC3.60/opt/aCC/include_std/iostream_compat/iostream.h",
line 4 # #warning is being replaced by followed by
"using namespace std;"
#warning is being replaced by followed by "using namespace std;"

-Bharath