Re: oaf gnome-factory problems



Hi Rodrigo and Mathieu:

On 11 Aug 2000, Mathieu Lacage wrote:

> Rodrigo Moya <rodrigo@linuxave.net> writes:
> 
> > Hi all!
> > 
> > I am trying to compile a program which makes use of GnomeFactory, and
> > which compiled and run successfully with gnorba, but now with OAF I get
> > these errors:
> > 
> > ../../lib/gda-server/.libs/libgda-server.so: undefined reference to
> > `POA_GNOME_GenericFactory__fini'
> > ../../lib/gda-server/.libs/libgda-server.so: undefined reference to
> > `_ORBIT_skel_GNOME_GenericFactory_create_object'
> > ../../lib/gda-server/.libs/libgda-server.so: undefined reference to
> > `POA_GNOME_GenericFactory__init'
> > ../../lib/gda-server/.libs/libgda-server.so: undefined reference to
> > `_ORBIT_GNOME_GenericFactory_CannotActivate_marshal'
> > ../../lib/gda-server/.libs/libgda-server.so: undefined reference to
> > `_ORBIT_skel_GNOME_GenericFactory_supports'
> > 
> > as I was told by Michael, this is very strange, but, if I run:
> > 
> > [rodrigo@txalaparta] nm /usr/lib/liboaf.so.0.0.0 | grep GenericFactory
> > 0000b7e0 T GNOME_GenericFactory_CannotActivate__free
> > 00010560 D GNOME_GenericFactory__classid
> > 0000b3c0 T GNOME_GenericFactory_create_object
> > 0000b1d0 T GNOME_GenericFactory_supports
> > 00010520 D TC_GNOME_GenericFactory_CannotActivate_struct
> > 000104e0 D TC_GNOME_GenericFactory_struct
> > 0000b1a0 T _ORBIT_GNOME_GenericFactory_CannotActivate_demarshal
> > 
> > so those functions are not in liboaf nor in the files generated by
> > orbit-idl. where are they?
> 
> I think they are in the skeletons of the factory. 
> 
no doubt ;-)

> liboaf does not link against the skeletons of the factory because it does 
> not use them. I guess you are trying to implement a factory yourself, no ?
> 
> If so, we can fix this in the upcomming release by making liboaf link
> against oaf-factory-skels.c (add it in liboaf/Makefile.am -> source section)
> 

I'm sorry if I am writting garbage, but, shouldn't it be
gnome-factory-skels.c? In fact, correct my if I am wrong, but liboaf
should not include it if it does not use it. The programmer of a new
factory should include it, as happens with any implementation of a CORBA
server that a programmer wants to write based in the skeletons, of course.

> If this fixes your problem, I think maciej will be happy to make it work 
> for you, (we already discussed this sooner and he agreed with me: we can do 
> it :)
> 
> Mathieu
> 
> > 
> > What am I doing wrong?
> > 
> > cheers
> > 

	Regards.
	diego.

-- 
Diego Sevilla Ruiz - http://ditec.um.es/~dsevilla/ - dsevilla@um.es
Departamento de Ingeniería y Tecnología de Computadores
Facultad de Informática. Universidad de Murcia
Campus de Espinardo - 30080 Murcia (SPAIN). Tel. +34-968-367570
\huge d\em\kern-.36em\lower-.2ex\hbox{\small sevilla}\kern-.1em@um.es

$_="\\l/) (>".     "_'\n<";@@=        /.|\n/g;$_=
"\@".     "\007f".   "DDq".           "DD5".   "\204".
"\@".     "DT4CE".    "D54E".         "DD".    "\244".
"\021".   "dBDTC".     "\010DD".      "\200\$FD\024".
"GDAG".   "DAGDT".       "CqI";$c     =0;$p    =5;for$q
(/./g)    {$q=              ord$q;    for(a,   b){$z[$c]
=$@[$p+=($q&15)    -4];$q>>=4;$c+=33  ;$c>98   &&($c-=98);}};print@z;





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