[MOAB-dev] [PyNE] Install instructions with MOAB for MCNP?

Fri Mar 21 10:50:00 CDT 2014

You shouldn't set MOAB_INCLUDE_DIRS or MOAB_LIBRARIES to cache
variables. With them not being cache variables you can also remove the
logic to check if they exist, since it won't be needed.

On Fri, Mar 21, 2014 at 11:21 AM, Anthony Scopatz <scopatz at gmail.com> wrote:
>
> On Fri, Mar 21, 2014 at 9:45 AM, Vijay S. Mahadevan <vijay.m at gmail.com>
> wrote:
>>
>> Where is FindMOAB.cmake and how is that currently being used ? We
>> could give you a template for usage but this depends on some other
>> things detailed below.
>
>
> HI Vijay!
>
> Here is our FindMOAB.cmake file:
> https://github.com/pyne/pyne/blob/staging/cmake/FindMOAB.cmake
> I am not sure if this is really sufficient.
>
>>
>> There are additions/fixes to the current CMake build system in the
>> pipeline along with some major autoconf changes to enhance the current
>> configuration capability. It is possible that the current
>> MOABConfig.cmake file generated out of autoconf is insufficient to
>> fully describe the configuration when used from downstream codes. I'll
>> be merging the outstanding CMake changes (within the next week or so),
>> which will hopefully fix some simple configuration issues.
>
>
>
>>
>> I can also create a FindMOAB.cmake for consumption by other codes using
>> MOAB if
>> that will be useful.
>
>
> This would be super useful!  We would use this immediately.  Thanks!
>
> Be Well
> Anthony
>
>>
>>
>> Vijay
>>
>>
>> On Thu, Mar 20, 2014 at 10:50 PM, Anthony Scopatz <scopatz at gmail.com>
>> wrote:
>> >
>> > On Sat, Mar 15, 2014 at 4:52 PM, Andrew Davis
>> > <andrewdavis.davis at gmail.com>
>> > wrote:
>> >>
>> >> Comping with verbose mode suggests that headers variable is not set
>> >> correctly
>> >>
>> >> cd /data/opt/pyne/build/pyne && /usr/bin/c++   -D_dagmc_EXPORTS
>> >> -D__LINUX__ -DJSON_IS_AMALGAMATION -O3 -DNDEBUG -fPIC
>> >> -I/data/opt/dagmc/hdf5/include
>> >> -I/usr/lib/python2.7/dist-packages/numpy/core/include
>> >> -I/data/opt/pyne/cpp
>> >> -I/usr/include/python2.7    -o CMakeFiles/_dagmc.dir/_dagmc.cxx.o -c
>> >> /data/opt/pyne/build/pyne/_dagmc.cxx
>> >>
>> >
>> >>
>> >> So is there somekind of mismatch between the MOAB_INCLUDE_DIRS env
>> >> wanted
>> >> by cmake/FindMOAB and the MOAB_INCLUDE_DIR suggested by the cmake build
>> >> echo.
>> >
>> >
>> > Hey Andy,
>> >
>> > There very well might be.  I am not super confident in the
>> > FindMOAB.cmake.
>> > This seems like the thing that MOAB itself should support. Maybe they do
>> > and
>> > I missed it when I wrote the dagmc wrapper. For expediency, I just used
>> > the
>> > best thing that I found online.  It could probably use love & official
>> > support.
>> >
>> > Be Well
>> > Anthony
>> >
>> >>
>> >>
>> >> Andy
>> >>
>> >>
>> >>
>> >>
>> >> On Sat, Mar 15, 2014 at 4:44 PM, Andrew Davis
>> >> <andrewdavis.davis at gmail.com> wrote:
>> >>>
>> >>> Can anyone confirm is this is true? When I try it I get the following
>> >>>
>> >>>     python setup.py install --user --
>> >>> -DMOAB_INCLUDE_DIR=/data/opt/dagmc/moab/include
>> >>> -DMOAB_LIBRARY=/data/opt/dagmc/moab/lib/libMOAB.so
>> >>>
>> >>> It finds MOAB,
>> >>>
>> >>> -- Found MOAB: /data/opt/dagmc/moab/lib/libMOAB.so
>> >>> -- MOAB header files: /data/opt/dagmc/moab/include
>> >>> -- MOAB library: /data/opt/dagmc/moab/lib/libMOAB.so
>> >>> -- MOAB Found: TRUE
>> >>>
>> >>> Then fails during build
>> >>>
>> >>> /data/opt/pyne/build/pyne/_dagmc.cxx:322:26: fatal error:
>> >>> moab/Types.hpp:
>> >>> No such file or directory
>> >>>  #include "moab/Types.hpp"
>> >>>                           ^
>> >>> compilation terminated.
>> >>> make[2]: *** [pyne/CMakeFiles/_dagmc.dir/_dagmc.cxx.o] Error 1
>> >>> make[1]: *** [pyne/CMakeFiles/_dagmc.dir/all] Error 2
>> >>> make: *** [all] Error 2
>> >>> Traceback (most recent call last):
>> >>>   File "setup.py", line 106, in <module>
>> >>>     main()
>> >>>   File "setup.py", line 100, in main
>> >>>     main_body()
>> >>>   File "setup.py", line 91, in main_body
>> >>>     rtn = subprocess.check_call(['make'] + make_args, cwd='build')
>> >>>   File "/usr/lib/python2.7/subprocess.py", line 540, in check_call
>> >>>     raise CalledProcessError(retcode, cmd)
>> >>> subprocess.CalledProcessError: Command '['make']' returned non-zero
>> >>> exit
>> >>> status 2
>> >>>
>> >>> My MOAB is setup correctly, this is a fresh pull from staging, I can
>> >>> confirm that the header is where it should be.
>> >>>
>> >>> Any ideas?
>> >>>
>> >>> Thanks
>> >>>
>> >>> Andy
>> >>>
>> >>>
>> >>> On Mon, Mar 10, 2014 at 1:31 PM, Elliott Biondo <Biondo at wisc.edu>
>> >>> wrote:
>> >>>>
>> >>>> I actually ran into this last week. Anthony helped me with the cmake
>> >>>> flags:
>> >>>>
>> >>>> python setup.py install --user --
>> >>>> -DMOAB_INCLUDE_DIR=/PATH/TO/MOAB/include
>> >>>> -DMOAB_LIBRARY=/PATH/TO/MOAB/lib/libMOAB.so
>> >>>>
>> >>>>
>> >>>> On Mon, Mar 10, 2014 at 12:42 PM, Matthew Gidden <gidden at wisc.edu>
>> >>>> wrote:
>> >>>>>
>> >>>>> It will involve setting pyne's cmake flags, where the setup looks
>> >>>>> like
>> >>>>>
>> >>>>> ```
>> >>>>> setup.py install <python flags> -- <cmake flags>
>> >>>>> ```
>> >>>>>
>> >>>>> You can see such an example in moab_build.sh in pyne-ci.
>> >>>>>
>> >>>>>
>> >>>>> On Mon, Mar 10, 2014 at 12:41 PM, Paul Wilson
>> >>>>> <wilsonp at engr.wisc.edu>
>> >>>>> wrote:
>> >>>>>>
>> >>>>>> Hmmmm...  I guess I can look in the pyne-ci repo... I'll do that.
>> >>>>>>
>> >>>>>> Paul
>> >>>>>>
>> >>>>>>
>> >>>>>> On 03/10/2014 12:31 PM, Paul Wilson wrote:
>> >>>>>>>
>> >>>>>>> Hi all,
>> >>>>>>>
>> >>>>>>> Do we have any install instructions that describe how to pass the
>> >>>>>>> right path and variable info to build PyNE with MOAB?  I don't see
>> >>>>>>> it at
>> >>>>>>> pyne.io or the README.
>> >>>>>>>
>> >>>>>>> Paul
>> >>>>>>>
>> >>>>>>
>> >>>>>> --
>> >>>>>> -- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
>> >>>>>> ~
>> >>>>>> --
>> >>>>>> Paul Wilson ~ UW-Madison ~ 608-263-0807 ~ cal:
>> >>>>>> http://bit.ly/pphw-cal
>> >>>>>> Professor, Engineering Physics. ~ http://cnerg.engr.wisc.edu
>> >>>>>> Faculty Director, Advanced Computing Infrastructure
>> >>>>>>
>> >>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> --
>> >>>>> Matthew Gidden
>> >>>>> Ph.D. Candidate, Nuclear Engineering
>> >>>>> The University of Wisconsin -- Madison
>> >>>>> Ph. 225.892.3192
>> >>>>>
>> >>>>> --
>> >>>>>
>> >>>>> ---
>> >>>>> You received this message because you are subscribed to the Google
>> >>>>> Groups "PyNE" group.
>> >>>>> To unsubscribe from this group and stop receiving emails from it,
>> >>>>> send
>> >>>>> an email to pyne-dev+unsubscribe at googlegroups.com.
>> >>>>> For more options, visit https://groups.google.com/d/optout.
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> Elliott D. Biondo
>> >>>> Nuclear Regulatory Commission Fellow
>> >>>> Computational Nuclear Engineering Research Group (CNERG)
>> >>>> Department of Nuclear Engineering and Engineering Physics
>> >>>> University of Wisconsin - Madison
>> >>>>
>> >>>> 434 Engineering Research Building
>> >>>> 1500 Engineering Drive
>> >>>> Madison, WI 53706
>> >>>>
>> >>>> Calendar
>> >>>>
>> >>>> --
>> >>>>
>> >>>> ---
>> >>>> You received this message because you are subscribed to the Google
>> >>>> Groups "PyNE" group.
>> >>>> To unsubscribe from this group and stop receiving emails from it,
>> >>>> send
>> >>>> an email to pyne-dev+unsubscribe at googlegroups.com.
>> >>>> For more options, visit https://groups.google.com/d/optout.
>> >>>
>> >>>
>> >>
>> >> --
>> >>
>> >> ---
>> >> You received this message because you are subscribed to the Google
>> >> Groups
>> >> "PyNE" group.
>> >> To unsubscribe from this group and stop receiving emails from it, send
>> >> an
>> >> email to pyne-dev+unsubscribe at googlegroups.com.
>> >> For more options, visit https://groups.google.com/d/optout.
>> >
>> >
>
>