Re: [orbitcpp-list] orbit requires gcc 2.95.2+?
Status: Beta
Brought to you by:
philipd
From: Phil D. <ph...@us...> - 2000-11-07 12:00:08
|
la...@se... writes: > Thanks for the quick reply! > > Phil Dawes wrote: > > > Hi lance, > > > > There really isn't much point regressing to orbitcpp-0.24 - there's > > not a huge amount of functionality in that release and it's not > > supported. > > Good news - I've got 0.27 built and examples running (tho having > some troubles running them accross two machines at the moment, > even with care to copy the server's ior file). > You have to enable TCP/IIOP support explicitly - the gnome folks disabled this in ORBit by default because it might be a 'security hole'. I think you need to pass -ORBIIOPIPv4=1 or something. It's in the orbit faq: http://orbit-resource.sourceforge.net/faq.html > > I'm confused as to why you're locked into stock compilers - I've > > upgraded many a rh6 system to gcc 2.95.2 (well 4 anyway :-). > > > > These are the rpms I've got: > > > > gcc-2.95.2-3.i386.rpm > > gcc-c++-2.95.2-3.i386.rpm > > cpp-2.95.2-3.i386.rpm > > libstdc++-2.95.2-3.i386.rpm > > libstdc++-compat-2.95.2-3.i386.rpm > > libstdc++-devel-2.95.2-3.i386.rpm > > Hmmm, perhaps I shall try it again. The initial problem I had > was misinfo - I thought 2.95.2 was not object/link compatible > (perhaps that's 2.96) as I'll need to link with others and their > objects from 2.91. Installing libstdc++-compat-2.95.2-3.i386.rpm sorted these sort of problems for me. Hope this helps, Phil |