[omniORB] Linking errors under Cygwin using omniORB 4.1.2

[julio teca]

Hello there,

I am trying to get omniORB 4.1.2 working under Cygwin 2.573.2.2
with gcc 3.4.4 (cygming special, gdc 0.12, using dmd 0.125).

I have compiled flawlessly from scratch openssl 0.9.8h, doing a shared
build. The libraries have been installed in /usr/local/ssl. The only
incidence
was that I had to install cygwin's package ccrypt, since openssl asked
me for cygcrypto-0.9.8.dll. After that all worked.

When compiling omniORB I had to modify the file src/tool/dir.mk, removing
the "omkdepend" from:

ifdef UnixPlatform
SUBDIRS = omkdepend omniidl
endif

that as far as I know is not necessary in Win32. For some reason,
UnixPlatform
is detected. Then I followed these steps (being at the omniORB root
directory):

./configure --with-openssl=/usr/local/ssl

This command detected my architecture i686-pc-cygwin, and the openssl
installation. Then I used:

make && make install

It compiled and installed perfectly well. The problems came when I tried to
compile a simple client application that uses ssl (which is working under
GNU
Linux and omniORB 4.1.2):

g++ -o client client.o HelloSk.o -lomniORB4 -lomnithread -lomniDynamic4
-lomnisslTP4 -Wall -L/usr/local/lib

I got the following error:

/usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld:
warning: auto-importing has been activated without --enable-auto-import
specified on the command line.
This should work unless it involves constant data structures referencing
symbols from auto-imported DLLs.Info: resolving
sslContext::certificate_authority_file        by linking to
__imp___ZN10sslContext26certificate_authority_fileE (auto-import)
Info: resolving sslContext::key_file       by linking to
__imp___ZN10sslContext8key_fileE (auto-import)
Info: resolving sslContext::key_file_password        by linking to
__imp___ZN10sslContext17key_file_passwordE (auto-import)
Info: resolving _CORBA_String_helper::empty_string        by linking to
__imp___ZN20_CORBA_String_helper12empty_stringE (auto-import)
Info: resolving __omni_omnisslTP_should_be_linked_but_is_not_ by linking to
__imp___omni_omnisslTP_should_be_linked_but_is_not_ (auto-import)
Info: resolving CORBA::Object::_PR_magic     by linking to
__imp___ZN5CORBA6Object9_PR_magicE (auto-import)
Info: resolving vtable for CORBA::Objectby linking to
__imp___ZTVN5CORBA6ObjectE (auto-import)
Info: resolving CORBA::Object::_PD_repoId      by linking to
__imp___ZN5CORBA6Object10_PD_repoIdE (auto-import)
Info: resolving vtable for omniCallDescriptorby linking to
__imp___ZTV18omniCallDescriptor (auto-import)
Info: resolving omni::omniORB_4_1       by linking to
__imp___ZN4omni11omniORB_4_1E (auto-import)

Any directions, or hints, would be really appreciated. I have been revising
the mailing list, and it
seems that I am not the only one with this kind of problem. Unfortunately
any solutions were
provided in the past.

Thank you
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20080605/8f321693/attachment.htm