On Tue, Apr 2, 2013 at 3:22 PM, Cody Permann <codypermann@gmail.com> wrote:
Trying this now...

On Tue, Apr 2, 2013 at 3:17 PM, Kirk, Benjamin (JSC-EG311) <benjamin.kirk-1@nasa.gov> wrote:
On Apr 2, 2013, at 4:12 PM, "Kirk, Benjamin (JSC-EG311)" <benjamin.kirk-1@nasa.gov> wrote:

> RemoteElem should be being created from LibMeshInit (see the Singleton::create() call and related bits in remote_elem.C) but apparently it isn't?

Yeah - bad news... RemoteElem::create() is _not_ being called on several of our systems.  Of course LibMeshInit is, but for some 
reason it's not getting all the way down into those new functions.

On this particular system I'm using GCC 4.5.1 which is a terrible compiler, but that's one data point.  The system that I have here where it is working is GCC 4.6.3.  Our build boxes are 4.7.2 and they are also failing so.... hard to draw conclusions other than something isn't working quite right. ;)



To be more clear, Singleton::setup() should call the preregistered  RemoteElemSetup::setup() function, which should create the remote_elem.  All that is in remote_elem.C - maybe put a trace in the RemoteElem::create() method and see what gives??