Re: [moose-generic] MOOSE_installation_problem

[Vadim A <ast...@nc...>]

When I compile, I always see lines with g++


g++ -g -pthread -fpermissive -fno-strict-aliasing -fPIC -fno-inline-functions -Wall -Wno-long-long -pedantic -DDO_UNIT_TESTS -DUSE_GENESIS_PARSER -DSVN_REVISION=\"4401M\" -DLINUX -DUSE_GSL -I /home/diag/opt/gsl/1.15/gnu/include/    basecode/_basecode.o msg/_msg.o shell/_shell.o biophysics/_biophysics.o hsolve/_hsolve.o randnum/_randnum.o scheduling/_scheduling.o builtins/_builtins.o device/_device.o kinetics/_kinetics.o ksolve/_ksolve.o regressionTests/_rt.o utility/_utility.o geom/_geom.o mesh/_mesh.o manager/_manager.o signeur/_signeur.o     -L/usr/lib -L/usr/local/lib -lpthread -L/lib64 -L/usr/lib64 -L/usr/lib -L/home/diag/opt/gsl/1.15/gnu/lib/ -lgsl -lgslcblas -lm -o moose



That tells me that I am using g++ (which is gcc) but not Intel compiler, right ?

So, I kind of confused what should I do here.

V.


On Mar 27, 2013, at 11:34 PM, Subhasis Ray wrote:

> Dear Vadim,
> 
> On 3/28/13, Vadim A <ast...@nc...> wrote:
>> 1. I modified the code
>> 
>>    /// Go through all elements under /classes and ask for defining a
>>    /// Python class for it.
>>    static int defineAllClasses(PyObject * module_dict)
>>    {
>>        ///static vector <Id> classes(Field< vector<Id>
>>> ::get(ObjId("/classes"),"children"));
>>        static const string children("children");
>>        static const string path("/classes");
>>        static const ObjId cle(path);
>>        assert(!(cle == ObjId::bad()));
>>        static vector <Id> classes = Field<vector<Id> >::get(cle,children);
>>        //static vector <Id> classes = Field<vector<Id>
>>> ::get(ObjId(path),children);
>> 
>> 
>> 
>> What should I expect to see with that assert ? I did not noticed any
>> differences when I did compile and import.
>> 
>> 
> 
> I was suspecting a static initialization order issue. Had the
> "/classes" element not been created by the time defineAllClasses tries
> to access it, the program would have exited with an assertion failure
> in stead of segmentation fault. But  from your results it does not
> seem to be the problem.
> 
>> 
>> Also, when I do inspect core , I do see some references to Intel compiler,
>> can it be indication of some problem ?
>> 
> 
> Since gdb is loading libraries related to intel compiler before
> python, is it possible that you built  Python with intel compiler? In
> that case can you see if rebuilding it with gcc and then building
> moose helps?
> 
> Best,
>  Subha
>