Hello Adam,

Le mercredi 05 mars 2008 à 07:34 -0500, Adam C Powell IV a écrit :
> I'm not getting this error...  I don't know why you would have seen that
> MPI error, I'd patched openmpi before but upgrading to 1.2.5-2 undid my
> patch and it works for me.  I reapplied my patch to hdf5 1.6.5-5.2
> (minus the changelog bit) and retried, and didn't see your error; 

Okay, got it: /usr/lib/libmpi++.so is an aternative registered with
liblam++.so (which was needed for hdf5 compilation). Maybe salome should
build-conflict with lam4-dev?

Hmmm... removing lam-dev makes /usr/lib/libmpi++.so an alternative
symlink to libpmpich++.so.1.0, and not to libmpi_cxx.so.0.0.0. It seems
only libmpi_cxx.so works: I have forced the symlink and the link error
disappeared.

> the error I'm getting now is a bit further down in TestContainer:
> 
> g++ "-DPACKAGE_NAME=\"Salome2 Project\"" -DPACKAGE_TARNAME=\"salome\" 
> -DPACKAGE_VERSION=\"3.2.5\" "-DPACKAGE_STRING=\"Salome2 Project 3.2.5\"" 
> -DPACKAGE_BUGREPORT=\"[EMAIL PROTECTED]" -DPACKAGE=\"salome\" 
> -DVERSION=\"3.2.5\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 
> -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 
> -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 
> -DHAVE_LIBDL=1 -DHAVE_LIBRT=1 -DHAVE_LIBM=1 -DHAVE_NAMESPACES= 
> -DHAVE_PTHREAD=1 -D__x86__=1 -D__linux__=1 -D__OSVERSION__=1 -DOMNIORB=1 
> -DCORBA_HAVE_POA=1 -DCORBA_ORB_INIT_HAVE_3_ARGS=1 
> -DCORBA_ORB_INIT_THIRD_ARG=\"omniORB\" -DRM=\"/bin/rm\" -DSH=\"/bin/sh\" 
> -DCP=\"/bin/cp\" -DRSH=\"/usr/bin/rsh\" -DRCP=\"/usr/bin/rcp\" 
> -DSSH=\"/bin/false\" -DSCP=\"/bin/false\" -I. -I./../Basics 
> -I./../SALOMELocalTrace -I./../NamingService -I./../Utils -I./../Registry 
> -I./../Notification -I./../ResourcesManager -I./../Container 
> -I../../salome_adm/unix -I../../idl -DOMNIORB_VERSION=4 -D__x86__ -D__linux__ 
> -DCOMP_CORBA_DOUBLE -DCOMP_CORBA_LONG -I/usr/include -I/usr/include/omniORB4 
> -I/usr/include/COS -DHAVE_MPI2 -DHAVE_SOCKET -m64 -D_OCC64 -g -D_DEBUG_ 
> -Wno-deprecated -Wparentheses -Wreturn-type -Wunused -pthread -MT 
> libSalomeTestComponentEngine_la-SALOME_TestComponent_i.lo -MD -MP -MF 
> .deps/libSalomeTestComponentEngine_la-SALOME_TestComponent_i.Tpo -c 
> SALOME_TestComponent_i.cxx  -fPIC -DPIC -o 
> .libs/libSalomeTestComponentEngine_la-SALOME_TestComponent_i.o
> SALOME_TestComponent_i.cxx: In constructor 
> ‘Engines_TestComponent_i::Engines_TestComponent_i(CORBA::ORB*, 
> PortableServer::POA*, PortableServer::ObjectId*, const char*, const char*)’:
> SALOME_TestComponent_i.cxx:47: error: ‘pd_refCount’ was not declared in this 
> scope
> SALOME_TestComponent_i.cxx: In member function ‘virtual char* 
> Engines_TestComponent_i::Coucou(CORBA::Long)’:
> SALOME_TestComponent_i.cxx:63: error: ‘pd_refCount’ was not declared in this 
> scope
> SALOME_TestComponent_i.cxx: In member function ‘virtual void 
> Engines_TestComponent_i::Setenv()’:
> SALOME_TestComponent_i.cxx:85: warning: unused variable ‘ret’
> SALOME_TestComponent_i.cxx:70: warning: unused variable ‘overwrite’
> make[3]: *** [libSalomeTestComponentEngine_la-SALOME_TestComponent_i.lo] 
> Error 1
> make[3]: Leaving directory 
> `/home/hazelsct/salome-3.2.6/KERNEL_SRC_3.2.6/src/TestContainer'
> 
> Any ideas on this? 

yes: pd_refCount, which was defined as the reference count in
RefCountServantBase is now named _pd_refCount in ServantBase. That's the
only occurrence of pd_refCount in Salomé sources.

My box is still compiling Salomé...

Regards,

Thomas


--- salome-3.2.6.orig/KERNEL_SRC_3.2.6/src/TestContainer/SALOME_TestComponent_i.cxx
+++ salome-3.2.6/KERNEL_SRC_3.2.6/src/TestContainer/SALOME_TestComponent_i.cxx
@@ -44,7 +44,7 @@
   MESSAGE("activate object");
   _thisObj = this ;
   _id = _poa->activate_object(_thisObj);
-  SCRUTE(pd_refCount);
+  SCRUTE(_pd_refCount);
 }
 
 Engines_TestComponent_i::Engines_TestComponent_i()
@@ -60,7 +60,7 @@
 {
   char s[100];
   sprintf(s, "TestComponent_i : L = %ld", (long) L);
-  SCRUTE(pd_refCount);
+  SCRUTE(_pd_refCount);
 
   return CORBA::string_dup(s);
 }

Reply via email to