Re: orbit-idl-2 ... Anyone?



 Hi all,
 
  I'm still strugling with this problem. I have as of yet not been able
 to compile gnome 2.0 (head) via vicius-build-scripts or garnome. It
 constantly bombs out as described in the attachment.
 
 Please, I've tried to get started to help developing gnome for months
 now, but I have no working experience with CORBA so this is too big a
 mouthfull for me - any help will be most appreciated!
 
   regards, Jan...
 
> fre, 2002-05-24 kl. 09:13 skrev Jan Vittrup Hansen:
> > Thank you for your response :)
> > 
> >   This is strange. I am simply using vicius-build-scripts to build gnome
> > head, and it stops here at ORBit2. I could find nothing interesting in
> > the config.log, and the command line that fails during make is shown
> > below.
> > 
> > ../../../src/idl-compiler/orbit-idl-2 -I../../../src/idl/CORBA_PIDL				-I../../../src/idl/CORBA					-I../../../src/idl/misc				
> > 	-I../../../src/idl/interop					--noskels --nodefskels --nostubs
> > --noidata --noheaders		--define=Object=OObject
> > --define=TypeCode=TTypeCode	        --showcpperrors --deps
> > ./.deps/iop-defs.idl.P iop-defs.idl 
> > 
> > This results in the complaints concerning GIOP.idl, which are included
> > by the file iop-defs.idl. Can you identify missing or superflous
> > options? Or are this simply not meant to be executed? 
> > 
> >  Regards, Jan...
> >  
> > 
> > fre, 2002-05-24 kl. 00:29 skrev Diego Sevilla Ruiz:
> > > Hi, Jan:
> > > 
> > > 	GIOP.idl is not IDL, but PIDL, so, it has special rules, and
> > > normally comes with precompiled versions ready to compile or either a
> > > special option in the IDL compiler to deal with PIDL. 
> > > 
> > > 	Normally, the files generated from PIDL cannot be obtained
> > > automatically, because they are different for every language (this is
> > > why it is called Pseudo-IDL).
> > > 
> > > 	So, your compilation shouldn't try to compile these IDL files.
> > > Perhaps is some error in the building process. Are you trying to compile
> > > ORBit2 itself or some other package with ORBit2?
> > > 
> > > 	Best regards.
> > > 	diego
> > > 
> > > On Thu, May 23, 2002 at 11:02:59PM +0200, Jan Vittrup Hansen wrote:
> > > 
> > > | Thank you for your response,
> > > | 
> > > |  The reason I ended up with this attempt at IDL is the problem of not
> > > | being able to compile the ORBit2 package, as reported earlier. Here the
> > > | system bombs out as presented below. The GIOP.idl has statements much
> > > | like the one I used in the test - can you suggest how this can be if the
> > > | example I made is not proper IDL? Can you attach your version of 
> > > | src/idl/interop/GIOP.idl for me to test?
> > > | 
> > > |  Regards Jan...
> > > | 
> > > | >head -40 ../../idl/interop/GIOP.idl |tail -1
> > > |      char                        magic [4];
> > > | 
> > > | >../../../src/idl-compiler/orbit-idl-2 -I../../../src/idl/CORBA_PIDL				-I../../../src/idl/CORBA					-I../../../src/idl/misc				
> > > | 	-I../../../src/idl/interop					--noskels --nodefskels --nostubs
> > > | --noidata --noheaders		--define=Object=OObject
> > > | --define=TypeCode=TTypeCode	        --showcpperrors --deps
> > > | ./.deps/iop-defs.idl.P iop-defs.idl 
> > > | orbit-idl 2.3.109 compiling
> > > |  small mode, show preprocessor errors, passes: common skel_impl imodule
> > > | 
> > > | ../../../src/idl/interop/GIOP.idl:40: Error: Zero array size is illegal
> > > | ../../../src/idl/interop/GIOP.idl:40: Error: Missing value in dimension
> > > | 1 of array `GIOP::MessageHeader_1_0::magic'
> > > | ../../../src/idl/interop/GIOP.idl:49: Error: Zero array size is illegal
> > > | ../../../src/idl/interop/GIOP.idl:49: Error: Missing value in dimension
> > > | 1 of array `GIOP::MessageHeader_1_1::magic'
> > > | ../../../src/idl/interop/GIOP.idl:74: Error: Zero array size is illegal
> > > | ../../../src/idl/interop/GIOP.idl:74: Error: Missing value in dimension
> > > | 1 of array `GIOP::RequestHeader_1_1::reserved'
> > > | ../../../src/idl/interop/GIOP.idl:97: Error: Zero array size is illegal
> > > | ../../../src/idl/interop/GIOP.idl:97: Error: Missing value in dimension
> > > | 1 of array `GIOP::RequestHeader_1_2::reserved'
> > > | 
> > > | ** (process:6992): WARNING **: iop-defs.idl compilation failed
> > > | 
> > > | 
> > > | tor, 2002-05-23 kl. 22:30 skrev Diego Sevilla Ruiz:
> > > | > Hi!
> > > | > 
> > > | > On Thu, May 23, 2002 at 10:13:14PM +0200, Jan Vittrup Hansen wrote:
> > > | > 
> > > | > | Hi,
> > > | > | 
> > > | > |  Still strugling. Dang. Now I made a small example. I don't get it.
> > > | > | Please anyone - have mercy! What can be at fault? Still running vicius
> > > | > | scripts, still no outside lib pollution according to strace :(
> > > | > | 
> > > | > |   regards, Jan...
> > > | > | 
> > > | > | >cat hop.idl
> > > | > | module test 
> > > | > | {
> > > | > |     struct leg
> > > | > | 	{
> > > | > | 		char hep[2];
> > > | > |     };
> > > | > | };
> > > | > | 
> > > | > 
> > > | > This is not valid IDL.
> > > | > 
> > > | > You should use something like:
> > > | > 
> > > | > typedef array<char,2> CharArray2;
> > > | > 
> > > | > struct leg {
> > > | > 	CharArray2 hep;
> > > | > };
> > > | > 
> > > | > 	Best regards.
> > > | > 	diego.
> > > | > 
> > > | > -- 
> > > | > Diego Sevilla Ruiz  http://ditec.um.es/~dsevilla  dsevilla@um.es  \    /\
> > > | > Dpto. Ingeniería y Tecnología de Computadores http://ditec.um.es   )  ( ')
> > > | > Visiting Extreme! Computing Lab       http://extreme.indiana.edu  (  /  )
> > > | > Indiana University, Bloomington               http://www.iub.edu   \(__)|
> > > | 
> > > | 
> > > | _______________________________________________
> > > | orbit-list mailing list
> > > | orbit-list@gnome.org
> > > | http://mail.gnome.org/mailman/listinfo/orbit-list
> > > 
> > > -- 
> > > Diego Sevilla Ruiz  http://ditec.um.es/~dsevilla  dsevilla@um.es  \    /\
> > > Dpto. Ingeniería y Tecnología de Computadores http://ditec.um.es   )  ( ')
> > > Visiting Extreme! Computing Lab       http://extreme.indiana.edu  (  /  )
> > > Indiana University, Bloomington               http://www.iub.edu   \(__)|


blah.txt.gz



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]