[omniORB] Upgrade to omniORB3 from omniORB280 DynSK.cc files aren't produce d by omniidl

Thu Oct 31 14:43:01 2002

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C280EB.C2BD4910
Content-Type: text/plain;
	charset="iso-8859-1"

Upgrading to omniORB3 from omniORB280. When attempting to build my baseline,

which used to build under 280, the omniidl compiler doesn't produce the
*DynSK.cc files. 
Is there an option different to omniORB3 as opposed to omniORB280? Below is
a 
sample of the build output:

Translating app.idl
Compiling: appSK.cc
Translating app.idl
Compiling: appDynSK.cc
g++: appDynSK.cc: No such file or directory.

------_=_NextPart_001_01C280EB.C2BD4910
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>Upgrade to omniORB3 from omniORB280 DynSK.cc files aren't produced by omniidl</TITLE>
</HEAD>
<BODY>

Upgrading to omniORB3 from omniORB280. When attempting to build my baseline, 
 which used to build under 280, the omniidl compiler doesn't produce the *DynSK.cc files. 
 Is there an option different to omniORB3 as opposed to omniORB280? Below is a 
 sample of the build output:

<P><FONT SIZE=2>Translating app.idl</FONT>
<BR><FONT SIZE=2>Compiling: appSK.cc</FONT>
<BR><FONT SIZE=2>Translating app.idl</FONT>
<BR><FONT SIZE=2>Compiling: appDynSK.cc</FONT>
<BR><FONT SIZE=2>g++: appDynSK.cc: No such file or directory.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C280EB.C2BD4910--