[omniORB] Building omniORB 3.0.3 on Win2000 platforms
William H Jones
enjones@lerc.nasa.gov
Thu, 25 Apr 2002 11:40:27 -0400 (EDT)
Roumen,
1. I did not switch to omniORB until after I had Win2000 machines,
so I have never compiled it on an NT platform.
2. I don't recall anything that seemed a Win2000 problem, but sometimes
I forget problems after they are solved. I should keep a journal.
3. I appear to be using Cygwin V131 if that means anything to you. It
appears to have been downloaded in May of 2001. I don't recall
anything Win2000 specific about it, either.
4. I downloaded the full Python 2.1, probably about the same time and
put it in its own root directory.
5. I doubt it is your problem, but one thing I have occassionally had to
dodge is the desire of a lot of install programs to put things in
C:\Program Files\.... That idiot space in the directory name screws
up all sorts of scripts. Even MicroSoft doesn't seem to get it right
in its own .bat file interpreter. On the other hand, my MicroSoft
Visual C++ is installed in C:\Program Files\whatever, so maybe that
is not relevant here.
6. The only other area I could think to look at would be the environment
variables. I have noticed that Visual Workbench doesn't track the
PATH variable, but seems to maintain its own under
Tools > Options > Directories > Executables
Perhaps the cl compiler is irretrivably hooked into the Workbench
settings and is unable to get to something it needs to execute? I
don't see anything in your output to suggest that, but maybe. The
fact that a command line entered by hand from a prompt works while
one auto-generated by the wrapper doesn't sort of suggests an
environment problem.
Sorry I don't have your answer. Good luck,
Bill
--
Dr. William H. Jones
MS 5-11
NASA Lewis Research Center
21000 Brookpark Road
Cleveland, OH 44135
216 433 5862
Preferred: William.H.Jones@grc.nasa.gov
Hard code: enjones@witsend.grc.nasa.gov
Personal: whjones@apk.net
Project Integration Architecture:
http://www.grc.nasa.gov/WWW/price000/index.html
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
> From owner-omniorb-list@uk.research.att.com Thu Apr 25 11:04 EDT 2002
> From: "Ivanov, Roumen" <Roumen.Ivanov@drkw.com>
> To: "'omniorb list'" <omniorb-list@uk.research.att.com>
> Subject: RE: [omniORB] Building omniORB 3.0.3 on Win2000 platforms
> Date: Thu, 25 Apr 2002 15:01:44 +0200
> MIME-Version: 1.0
> X-Loop: omniorb-list@uk.research.att.com
>
> 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
>
>
>