[omniORB] Problem building 3.0.3 on WinNT

Lars Immisch lars@ibp.de
Fri, 23 Mar 2001 10:00:49 +0100


<nofill>Hi Roger,

> I know I've probably overlooked something obvious but...
>  
> Trying to build omniORB 3.0.3 from source, using the gnuwin & python lite
> packages from the omniORB site, on an NT4 Intel box with MSVC6, I'm getting
> a memory access violation from omniidl.exe and the following build error:
> 
> make[2]: Entering directory `/omni/src/lib/omniORB2'
> ../../../bin/x86_win32/oidlwrapper.exe -gnuwin32 -bcxx -Wbh=.hh -Wbs=SK.cc
> -Wba -p../../../src/lib/omniORB2  -ComniORB3 ../../../idl/Naming.idl
> PYTHONPATH=(null)
> ..\..\..\bin\x86_win32\omniidl -bcxx -Wbh=.hh -Wbs=SK.cc -Wba
> -p..\..\..\src\lib \omniORB2 -ComniORB3 ..\..\..\idl\Naming.idl
> ..\..\..\bin\x86_win32\omnicpp: stdout: Bad file descriptor
> make[2]: *** [omniORB3/Naming.hh] Error 5
> make[2]: Leaving directory `/omni/src/lib/omniORB2'
> make[1]: *** [export] Error 2
> make[1]: Leaving directory `/omni/src/lib'
> make: *** [export] Error 2
</nofill>

Are you building debug binaries by any chance, that is, did you set
BuildDebugBianries=1 in one of the config files? (I think it was
mk/config.mk, but I could misremember things)


If you do, then this is a know problem. Set BuildDebugBinaries to 0 and
build again: make clean; make export.


- Lars