Re: [orbitcpp-list] orbit requires gcc 2.95.2+?

[Phil D. <ph...@us...>]

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.
 >