[omniORB] omniEvents1.0.3 vs. omniORB2.8 [supported?]

[Chang, Phyllis]

This is for SUN Solaris 5.6.

I passed the compiling by added the following two lines in the dir.mk of
omniEvents subdirectory:

AUXLIBS = Templates.DB/*.o
STL_INCLUDES= <where your STL library is located>

However, when I started "eventd", the following error message occurs:
"caught a system exception while resolving the naming services".

Therefore my question raise again, 

"Is omniEvents1.0.3 portable to omniORB2.8?"




Phyllis Chang
=====================================
AT&T Labs, IP Technology
2665 North First Street, Suite 300
San Jose, CA95134
USA

 



> -----Original Message-----
> From: Kriesten, Arnold (x5031) 
> [mailto:Arnold.Kriesten@arl.siemens.com]
> Sent: Tuesday, October 19, 1999 6:18 AM
> To: Chang, Phyllis
> Cc: omniorb-list@uk.research.att.com
> Subject: RE: [omniORB] omniEvents1.0.3 vs. omniORB2.8 [supported?]
> 
> 
> It runs fine under NT. I got with MSC++6.0 no link error messages.
> 
> Arnold
> 
> > -----Original Message-----
> > From: Chang, Phyllis [mailto:pxchang@ipo.att.com]
> > Sent: Monday, October 18, 1999 8:19 PM
> > To: 'Paul.Nader@alcatel.com.au'
> > Cc: 'omniorb-list@uk.research.att.com'
> > Subject: [omniORB] omniEvents1.0.3 vs. omniORB2.8 [supported?]
> > 
> > 
> > Paul,
> > 
> > I am a user of your omniEvent1.0.3 and omniORB2.7.1. Now I am 
> > upgrading
> > omniORB to 2.8, and I ran into some linking error while 
> > re-building the
> > eventd.
> > 
> > I noticed that from omniORB/contribution/omniEvents page, 
> there is no
> > information about the its portability to 2.8.
> > 
> > Do you have more information for me on this subject?
> > 
> > Thanks in advance.
> > 
> > 
> > BTW, attached is the error list. (sun solaris 5.6 and STL lib. from
> > http://www.stlport.org )
> > 
> > Phyllis Chang
> > AT&T Labs, IP Technology
> > 2665 North First Street, Suite 300
> > San Jose, CA95134
> > USA
> > 
> > pxchang@ipo.att.com
> > 408-576-3812	(o)
> > 
> >  <<error>> 
> > 
> > 
>