Thread: [orbitcpp-list] orbit requires gcc 2.95.2+?
Status: Beta
Brought to you by:
philipd
From: <la...@se...> - 2000-11-07 08:50:31
|
I'm locked into stock compilers on my Redhat 6.x system (gcc 2.91) but would really love to use orbitcpp. I've tried regressing to orbitcpp v0.24 which seems to be the last before the 2.95.2 compiler requirement, but that requires some python development environment. Any creative ideas on how to get a recent verion of orbitcpp working on a stock Redhat 6.x system with 2.91 compilers? I don't need any advance functinoality, and only the client is locked into 2.91. Can someone provide direction on installing the required python files (or tell me that this distant release is not worth installing)? If neither, perhaps reply with some pointers to other simple examples of using corba. Thx, -Lance. -- -=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=- Lance Welsh la...@se... Seascape Communications (650) 327-6890 -=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=- |
From: Phil D. <ph...@us...> - 2000-11-07 10:10:24
|
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. 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 Sorry that this is such a crap reply, but I really don't think it's worth your while attempting to compile that old release. Cheers, Phil la...@se... writes: > I'm locked into stock compilers on my Redhat 6.x system (gcc 2.91) > but would really love to use orbitcpp. I've tried regressing to orbitcpp > v0.24 which seems to be the last before the 2.95.2 compiler requirement, > but that requires some python development environment. > > Any creative ideas on how to get a recent verion of orbitcpp working > on a stock Redhat 6.x system with 2.91 compilers? I don't need any > advance functinoality, and only the client is locked into 2.91. > > Can someone provide direction on installing the required python files > (or tell me that this distant release is not worth installing)? > > If neither, perhaps reply with some pointers to other simple examples > of using corba. Thx, -Lance. > |
From: <la...@se...> - 2000-11-07 10:27:01
|
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). > 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. Secondly, when I installed a similar set to the above, the linker gave me unersolved symbols from libX11.so (something like getpum@@(GLIBC2_2) and setshm@@(GLIBC2_2)) and I freaked-out (I'm using an SGI PC). I don't think there's any new libX11 in the rpms above, so unless you steer me otherwise, I will see how far I get with 0.27. > Sorry that this is such a crap reply, but I really don't think it's > worth your while attempting to compile that old release. I greatly appreciate your reply. It's quite late here and I'm on the end of a 20 hour binge. I will look forward to rereading your reply in the morning and may even have the energy to retry new compilers. Thanks, -Lance. -=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=- Lance Welsh la...@se... Seascape Communications (650) 327-6890 -=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=- |
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 |
From: <la...@se...> - 2000-12-09 03:40:32
|
Phil Dawes wrote: > Installing libstdc++-compat-2.95.2-3.i386.rpm sorted these sort of > problems for me. Thanks for your thorough and thoughtful reply some time ago. It took me awhile to exaust all the possibilities, but I can not seem to get a compiler combo to compile orbitcpp-0.29's 'test' programs (although the rest such as 'compiler' and ' orb' compiler just fine). While I wasn't able to exactly replicate your system (I'm running SGI's version of redhat 6.1 linux which had the 2.91 compilers), I came up with these RPMs: cpp-2.95.2-4tr.i586.rpm libstdc++-2.95.2-4tr.i586.rpm gcc-2.95.2-4tr.i586.rpm libstdc++-compat-2.95.2-4tr.i586.rpm gcc-c++-2.95.2-4tr.i586.rpm libstdc++-devel-2.95.2-4tr.i586.rpm but I get errors compiling the 'test' programs, such as in 'boolean': /include -I/usr/include -g -O0 -Wall -c boolean-cpp-common.cc In file included from boolean-cpp-stubs.hh:11, from boolean-cpp-common.cc:6: boolean-cpp-common.hh:21: parse error before `<' boolean-cpp-common.hh:22: parse error before `<' make[1]: *** [boolean-cpp-common.o] Error 1 I'm sticking with orbitcpp-0.26 which works fine with me! The main problem I'm having (clients hanging on a reply from a dead server) is with orbit's generated 'C' files and not with the generated 'C++' files. I'm bemuzed as to how anyone has seriously used orbit in a fault-tolerant way! Thanks again, always, and anyways, -Lance. _______________________________________________ > orbitcpp-list mailing list > orb...@li... > http://lists.sourceforge.net/mailman/listinfo/orbitcpp-list -- -=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=- Lance Welsh la...@se... Seascape Communications (650) 327-6890 -=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=--=+=- |
From: Lance W. <la...@se...> - 2001-01-18 16:56:14
|
Does anyone have an example of inhertance? Compiling the IDL files seems to work (say ones that define base class 'A' and dereived class 'B'), but when trying to compile 'B_impl.cc" (which is derived from 'A_impl'), some structures from A's headers are redefined (indentically but fatally) by B's headers. Information or examples appreciated. Thanks, -Lance. |
From: Lance W. <la...@se...> - 2001-01-18 16:59:12
|
Pardon my subject of "Multiple Inheritance". I am in no way tryint to perform multiple inheritance - just a simple derivation of B from A. Thanks, -Lance. Lance Welsh wrote: > Does anyone have an example of inhertance? Compiling the IDL files seems to > work (say ones that define base class 'A' and dereived class 'B'), but when trying > to compile 'B_impl.cc" (which is derived from 'A_impl'), some structures from > A's headers are redefined (indentically but fatally) by B's headers. > Information or examples appreciated. Thanks, -Lance. > > _______________________________________________ > orbitcpp-list mailing list > orb...@li... > http://lists.sourceforge.net/lists/listinfo/orbitcpp-list |
From: Andreas K. <ak...@ix...> - 2001-01-18 17:22:57
|
On Thu, Jan 18, 2001 at 08:56:14AM -0800, Lance Welsh wrote: > Does anyone have an example of inhertance? Compiling the IDL files seems to > work (say ones that define base class 'A' and dereived class 'B'), but when trying > to compile 'B_impl.cc" (which is derived from 'A_impl'), some structures from > A's headers are redefined (indentically but fatally) by B's headers. > Information or examples appreciated. Thanks, -Lance. > > > _______________________________________________ > orbitcpp-list mailing list > orb...@li... > http://lists.sourceforge.net/lists/listinfo/orbitcpp-list > Hi Lance, IMHO, orbitcpp doesn't yet implement the #pragma inhibit directives properly (see CORBA spec or ORBit docs) so that for now the only solution would be to put all the definitions into one huge IDL file. (or #include them) This is a temporary deficiency, it will go away as we proceed. Bye Andy -- What do you have if you have 6 mathematicians buried up to their necks in pig shit? - Not enough pig shit. |