From: Jenny P. <p....@te...> - 2006-08-25 08:25:36
|
Hi I have actually called init_mib_modules from my code and I think it takes care of this automatically. So I need not explicitly call these two functions. I think that solves the problem. Thank you very much. Regards Jenny Magnus Fromreide wrote: >On Wed, Aug 23, 2006 at 02:47:12PM +0530, Jenny Paul wrote: > > >>Hi >> This is related to my previous question regarding >>init_vacm_vars(); and >>init_usmUser(); >> My application is wriiten in C++. When I compile using g++ I >>get compilation error as follows >> >>init_vacm_vars' undeclared (first use this function). >>init_usmUser' undeclared (first use this function). >> >> > >This means that the functions init_vacm_vars and init_usmUser aren't declared >as you readily can see by tring to find them in the headers. > >If a routine isn't in the public headers then I'd guess that the routine isn't >part of the public interface of the package - now I aam uncertain about >those routines, is their absence a concious decision or an accident? > > > >>The same compiles if I use gcc. I am using SuSE Linux 9.1. >>Is there anyway to compile it with g++? >> >> > >Quick and dirty workaround (really dirty): > >Add the following code in global scope before use: > >extern "C" { > void init_usmUser(void); > void init_vacm_vars(void); >} > >Then make sure to track if the functions do show up in the headers and remove >the hack. > >/MF > > > > > -- Thanks & Regards, Jenny Paul ------------------------------------ Teles Computer Systems India Pvt Ltd Indiranagar Bangalore - 560008 |