orbit(2)-idl



When I was compiling the 2.0 platform, I ran across an error in the oaf
build.  It turned out to be a symbol clash between ORBit and ORBit2 that
was created by the oaf configure script grabbing a 1.x version of
orbit-idl out of my path.  

I'm wondering if there is an elegant way to guard against this, or if we
need to rename orbit-idl to orbit2-idl for 2.0?

Mike




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