From: Dilawar S. <dil...@gm...> - 2013-08-01 01:19:20
|
Hi Subha, I checked-out the buildQ branch. Its working fine now. -- Dilawar EE, IITB On Wed, Jul 31, 2013 at 1:55 PM, Subhasis Ray <ray...@gm...>wrote: > Hi Dilawar, > > > > On Wed, Jul 31, 2013 at 1:13 PM, Dilawar Singh > <dil...@gm...>wrote: > > > > > I build the moose using `python setup.py build`. It complained about > > unavailability of two files 'ksolve/FuncTerm.cpp', and > > 'mesh/ChemMesh.cpp'. I removed them from `setuo_/__init__.py` file. It > got > > compiled. When importing moose into python, I am getting following error. > > > > ImportError: /usr/local/lib/python2.7/dist-packages/moose.so: undefined > > symbol: _ZN8ReacBase9setSolverE2IdS0_ > > > > What am I missing? > > > > > The distutils based setup is not actively maintained. The standard way to > build moose is: > > make moose > > in the top level directory and then you can add {moose}/python to your > PYTHONPATH variable. I am not sure what version of moose you are using, but > the latest development branch is buildQ. > > Best, > Subha > > ------------------------------------------------------------------------------ > Get your SQL database under version control now! > Version control is standard for application code, but databases havent > caught up. So what steps can you take to put your SQL databases under > version control? Why should you start doing it? Read more to find out. > http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk > _______________________________________________ > moose-devel mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moose-devel > |