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

Tue Jan 20 14:19:47 GMT 2004

Thanks for your experience.

I'm using MSVC6.0 with CYGWIN (1.5.5(0.94/3/2) 2003-09-20 16:31) . 
It's not an unresolved symbol issue that I have; I can even not build
the libraries !

I don't think it's a CYGWIN version issue.
Can you show me your mount point on CYGWIN ?
These are mine
>mount
$ mount
C:\cygwin\bin on /usr/bin type system (binmode)
C:\cygwin\lib on /usr/lib type system (binmode)
C:\cygwin on / type system (binmode)
h: on /home/fredp type user (binmode)
m: on /main/experimental type system (binmode)
q: on /site/local type user (binmode)
x: on /opt/experimental type user (binmode)
y: on /site/experimental type user (binmode)
c: on /cygdrive/c type user (binmode,noumount)
d: on /cygdrive/d type user (binmode,noumount)
f: on /cygdrive/f type user (binmode,noumount)
n: on /cygdrive/n type user (binmode,noumount)
o: on /cygdrive/o type user (binmode,noumount)
p: on /cygdrive/p type user (binmode,noumount)
w: on /cygdrive/w type user (binmode,noumount)
z: on /cygdrive/z type user (binmode,noumount)

I'm compiling omniORB on my drive D:\ which is mounted on /cygdrive/d 
I'm not sure of the binmode... I used to see exec in old CYGWIN ???!!

Thanks for your cooperation

Fred

-----Original Message-----
From: omniorb-list-bounces at omniorb-support.com
[mailto:omniorb-list-bounces at omniorb-support.com] On Behalf Of Ivanov,
Roumen
Sent: mardi 20 janvier 2004 13:40
To: omniorb-list at omniorb-support.com
Subject: RE: [omniORB] A lot of unresolved external symbols (OmniORB
4.0.3 )

Well, it compiled and linked now.
OmniOrb-4.0.3, Win2000, MSVC 7 (Visual C++ .NET - MDE 2003), Cygwin
1.5.5-1 release - almost full installation.

Regards,
Roumen Ivanov

-----Original Message-----
From: omniorb-list-bounces at omniorb-support.com
[mailto:omniorb-list-bounces at omniorb-support.com]On Behalf Of Ivanov,
Roumen
Sent: Tuesday, January 20, 2004 10:01
To: omniorb-list at omniorb-support.com
Subject: RE: [omniORB] A lot of unresolved external symbols (OmniORB
4.0.3 )

Hi all,
I'm experiencing same problems.
I could not find checkmount in my cygwin installation. Is it sure that
checkmount could help?
There is no clear way to identify what exactly do I need installing
cygwin. The full package is too big. The first time I got a cygwin
installation with no "make"! Then I just copied it from another
(Win2000) PC where it used to work.
Is somewhere some minimal cygwin available, which could be used only to
compile omniORB?

Thanks in anticipation,
Roumen Ivanov

-----Original Message-----
From: omniorb-list-bounces at omniorb-support.com
[mailto:omniorb-list-bounces at omniorb-support.com]On Behalf Of Malge
Nishant
Sent: Monday, December 01, 2003 08:52
To: Rolf C Stadheim; omniorb-list at omniorb-support.com
Subject: RE: [omniORB] A lot of unresolved external symbols (OmniORB
4.0.3 )

Hi Rolf,
    One of the main reason about these errors is the GNU setup.
Please run GNU's checkmount utility and and try to build.

Regards
Nishant

-----Original Message-----
From: Rolf C Stadheim [mailto:rcs at bgoark.no]
Sent: Monday, December 01, 2003 1:29 PM
To: omniorb-list at omniorb-support.com
Subject: [omniORB] A lot of unresolved external symbols (OmniORB 4.0.3)

----- Original Message ----- 
From: Rolf  <mailto:rolf.stadheim at bgoark.no> 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

------------------------------------------------------------------------
--------
The information contained herein is confidential and is intended solely
for the
addressee. Access by any other party is unauthorised without the express
written permission of the sender. If you are not the intended recipient,
please
contact the sender either via the company switchboard on +44 (0)20 7623
8000, or
via e-mail return. If you have received this e-mail in error or wish to
read our
e-mail disclaimer statement and monitoring policy, please refer to 
http://www.drkw.com/disc/email/ or contact the sender.
------------------------------------------------------------------------
--------

------------------------------------------------------------------------
--------
The information contained herein is confidential and is intended solely
for the
addressee. Access by any other party is unauthorised without the express
written permission of the sender. If you are not the intended recipient,
please
contact the sender either via the company switchboard on +44 (0)20 7623
8000, or
via e-mail return. If you have received this e-mail in error or wish to
read our
e-mail disclaimer statement and monitoring policy, please refer to 
http://www.drkw.com/disc/email/ or contact the sender.
------------------------------------------------------------------------
--------

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