[omniORB] compiling v4.0.x with MSVC++ v5 sp3

[baileyk at schneider.com]

I've successfully built omniORB v3.0.5 with MSVC++ v5.0 sp3, but I've also
made a concerted effort to compile omniORB v4.0.2 and the latest CVS
snapshot, and at this point I don't think it's going to happen.

There are many (at least 5) instances of an internal compiler error on
simple global variable definitions.  The first is (for 4.0.2)

initRefs.cc
initRefs.cc(172) : fatal error C1001: INTERNAL COMPILER ERROR
                (compiler file 'E:\utc\src\\P2\main.c', line 379)
    Please choose the Technical Support command on the Visual C++
    Help menu, or open the Technical Support help file for more information

I've tried rearranging the source code, re-writing the String_var
constructors, and various other hacks, but to no avail...

Researching this on the net finds this MS article

http://support.microsoft.com/support/kb/articles/q167/3/47.asp

However, that claims sp3 solves the problem.  The workaround (disable
global optimization) also fails.  I have found some reports that the phase
2 compiler from sp2 solves the problem, but I'd hate to try to downgrade.
This page

http://support.microsoft.com/support/kb/articles/q168/9/12.asp

does not appear to list any bug which is similar to what I'm seeing execpt
for 167347 which is the one they claim to have fixed in sp3.

As I commented out the lines which caused the internal compiler errors,
eventually I got more mundane errors concerning socket structure field
names.  So my opinion at this point is that the combination of omniORB
v4.0.x and MSVC++ v5 sp3 would be very challenging to make work.  I'd
suggest removing all mention of MSVC++ v5 from the READMEs.

Thanks,
Kendall