[omniORB] A lot of unresolved external symbols (OmniORB 4.0.3)

jon.kristensen at kongsberg.com jon.kristensen at kongsberg.com
Tue Dec 2 21:10:14 GMT 2003


Rolf,

This is very similar to what I experienced.
I made a posts on this on november 11th & 25th on the subject "omniORB 
4.0.2/4.0.3 build error on Win XP". The last post is included below:

I sent an email on November 11th complaining that omniORB 4.0.2 did not 
build on my XP machine. I have now downloaded 4.0.3 and saw see exactly 
the same thing. What happened is that the build process failed to link 
omniDynamic403_rt.dll. I got 632 unresolved symbols. 

I have now found that this was caused by me having the "bin\x86_win32" 
directory of a previous version of omniORB listed in my PATH variable. 
Once I removed that entry from the path, everything builds as expected.

Just wanted to inform you in case others experience the same.



With Regards
Jon Kristensen
Principal Engineer SW, AUV Depth
Hydroacoustic Division
Kongsberg maritime AS, Horten, Norway

Direct tel:     +47 33 02 39 34
Mobile:                 +47 99 20 39 34
Office:                 +47 33 02 38 00
Fax     :               +47 33 04 76 19
e-mail:                 jon.kristensen at kongsberg.com

http://www.kongsberg.com





"Rolf C Stadheim" <rcs at bgoark.no>
Tel: 
Sent by: omniorb-list-bounces at omniorb-support.com
01.12.2003 08:58
01.12.2003 08:58 CET

 
        To:     <omniorb-list at omniorb-support.com>
        cc: 
        Subject:        [omniORB] A lot of unresolved external symbols (OmniORB 4.0.3)


 
----- Original Message ----- 
From: Rolf C Stadheim 
To: omniorb-list at omniorb-support.com 
Sent: Friday, November 28, 2003 6:34 PM
Subject: A lot of unresolved external symbols (OmniORB 4.0.3)

When compiling OmniORB 4.0.3 I get a lot of (632 of them) unresolved 
external symbols.
 
Some of the missing symbols:
 
*  CosNaming::NamingContext::CannotProceed::insertToAnyFn ... referenced 
in function CosNaming::NamingContext::CannotProceed:: scalar deleting 
destructor
* CosNaming::NamingContext::CannotProceed::_NP_repoId ... referenced in 
function CosNaming::NamingContext::CannotProceed::CannotProceed
* CosNaming::NamingContext::NotFound::_NP_typeId ... 
* CosNaming::NamingContextExt_Helper::release ...
* CosNaming::NamingContext_Helper::release
* CosNaming::NamingContext::AlreadyBound::~AlreadyBound
* CosNaming::NamingContext::NotEmpty::_NP_marshal
* CosNaming::NamingContext::InvalidName::_NP_repoId
 
and so on (there were reported 632 unresolved external symbols).
 
When I compiled OmniORB 4.0.2 using the exact same procedure, and using 
the same compiler (Visual Studio 7, compiler version 13.00), it all went 
fine.
 
So what's changed in 4.0.3, and why all these missing external symbols?
 
Regards,
RCS
 _______________________________________________
omniORB-list mailing list
omniORB-list at omniorb-support.com
http://www.omniorb-support.com/mailman/listinfo/omniorb-list


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20031202/db66d1ff/attachment.htm


More information about the omniORB-list mailing list