[omniORB] Building omniORB 3.0.3 on Win2000 platforms

[Ivanov, Roumen]

Hi Bill,
Thanks for spending time to help.

I have compiled omniORB on NT many times although using the python minimal
set for windows instead of full Python installation.
Recently I'm trying to migrate to Windows 2000 using exactly x86_nt_4
platform, but I got the following when I started to compile:

$ make export
...
...
../../../../../bin/x86_win32/clwrapper -gnuwin32 -c -O2 -MD -DHAVE_CONFIG_H
-I. -I.  -I../../../../../include -D__WIN32__ -D__x86__
-D__NT__ -D__OSVERSION__=4 -Focexp.o cexp.c
cl -c -O2 -MD -DHAVE_CONFIG_H -I. -I. -I..\..\..\..\..\include -D__WIN32__
-D__x86__ -D__NT__ -D__OSVERSION__=4 -Focexp.o cexp.c
cl: Invalid argument
make[4]: *** [cexp.o] Error 1
...
...

The strange is that executing the pure cl command (on the same target in the
according directory) succeeds:

cl -c -O2 -MD -DHAVE_CONFIG_H -I. -I. -I..\..\..\..\..\include -D__WIN32__
-D__x86__ -D__NT__ -D__OSVERSION__=4 -Focexp.o cexp.c
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 12.00.8804 for 80x86
Copyright (C) Microsoft Corp 1984-1998. All rights reserved.

cexp.c

what made me thinking, that there is something Win 2000 specific that I need
to set.
Now when you are saying that you have been using x86_nt_4 I don't know.
Either the clwrapper gets the return from cl wrong or my cygwin version that
gets confused under windows 2000.

What Cygnus version are you using?

Thanks again,
Roumen




 -----Original Message-----
From: 	enjones@lerc.nasa.gov [mailto:enjones@lerc.nasa.gov] 
Sent:	Thursday, April 25, 2002 14:23
To:	omniorb-list@uk.research.att.com
Subject:	[omniORB] Building omniORB 3.0.3 on Win2000 platforms

Roumen,

  I built omniORB 3.0.3 last summer on my Windows 2000 5.00.2195 SP2
platforms with Visual C++ V6.0 and everything worked pretty much per
the instructions.  Mistakes that I did make are as follows.

  1.  In file <OmniRoot>\config\config.mk, the comment near the top
      says to uncomment one of the following platform lines for the
      target platform.  I mistakenly uncommented the comment for the
      WinNT platform, in addition to the intended "platform = " line
      further below.

  2.  Further down in config.mk, there is an invitation to uncomment a
      BuildDebugBinary line.  I never managed to make this work.  I
      leave it commented out routinely.

  3.  In file <OmniRoot>\mk\platforms\x86_nt_4.0.mk, the comment near
      the middle says to set the PYTHON variable to the path to python
      interpreter.  I mistakenly set it to the path to the directory
      in which the python interpreter resided, in my case

        /cygdrive/c/Python21

      but what it wants is the fully qualified path of the python
      executable,

        /cygdrive/c/Python21/python

      Apparently it doesn't want the trailing .exe, or I didn't try
      that and stopped at the first guess that worked.

      Also, note that the path seems to need to be in CygWin file
      form, that is /cygdrive/c/....  Probably this has something
      to do with the Unix-y nature of the build system internals.

  4.  When it comes time to make omniORB work, I think (but didn't
      prove) that SP2 to Windows 2000 is a necessary thing.  I think
      SP2 fixed some TCP/IP socket problems.  I had some socket code
      that magically began to work when I installed SP2 and I assume
      that omniORB would be depending on the same services.

Those are the only bumps I remember.  Hope it helps....

Good luck,

Bill

--

Dr. William H. Jones
MS 5-11
NASA Lewis Research Center
21000 Brookpark Road
Cleveland, OH 44135

Project Integration Architecture
http://www.grc.nasa.gov/WWW/price000/index.html

216 433 5862
Preferred:  William.H.Jones@lerc.nasa.gov
Hard code:  enjones@witsend.lerc.nasa.gov
Personal:   whjones@apk.net

No man is so fortunate but that, at the hour of his doom,
he will not have at least a few about him who are pleased
with the proceedings.
  -- Marcus Aurelius



> At 01:04 PM 04/25/2002 +0200, Ivanov, Roumen wrote:
> Hi,
> it seems that the search on the mail list archives is not functioning
> anymore or the archives have been possibly moved.
> I'm looking for help on compiling omniORB (3.0.2 or 4) on Windows 2000.
> 
> Any hints would be very appreciated?
> 
> Roumen
> 
> 
> 
> 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


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