File Error When Installing MOAB for DAGMC Using WSL2

Hello everyone. I’ve been trying to set up the necessary tools for importing CAD and mesh-based geometries into OpenMC, and I’ve been running into an issue when installing MOAB (a required dependency of DAGMC). I can follow the steps outlined on the DAGMC installation page until it comes to running the ‘autoreconf -fi’ command. When I try to do this, I get an error saying that the file MOABConfig.h.in cannot be found. I was under the impression that running ‘autoreconf’ should generate this file, so I’m not sure what to make of this. I’ve tried running ‘autoheader’ independently, and it returns the same error. I have not made any changes to the configure.ac file, and I have followed the instructions on the DAGMC page up to this point. A few of my colleagues have successfully set up MOAB on their machines recently, so it appears that the issue may have something to do with my setup specifically. If anyone has any advice on how to work around or resolve this issue, I’d very much appreciate it.
Some relevant specifications:

  • I am using Ubuntu through WSL2
  • The MOAB version I’d like to use is 5.1.0, as specified in the DAGMC instructions
  • I’m using autoconf version 2.71
  • I’m using libtool version 2.4.7

Again, thank you to anyone who may be able to help with this.

Hi Aidan
Having the same issue on Ubuntu/WSL - did you manage to solve this?

Hi,

you can try building moab with cmake, something like this

cd $HOME/dagmc_bld
mkdir -p MOAB/bld
cd MOAB
git clone https://bitbucket.org/fathomteam/moab
cd moab
git checkout Version5.1.0
cd ..
ln -s moab src
# cmake alternative
cmake src -B bld \
        -DENABLE_HDF5=ON \
        -DHDF5_ROOT=$HOME/dagmc_bld/HDF5 \
        -DCMAKE_INSTALL_PREFIX=$HOME/dagmc_bld/MOAB \
        -DENABLE_BLASLAPACK=OFF \
        -DBUILD_SHARED_LIBS=ON \
        -DENABLE_FORTRAN=OFF \
        -DENABLE_PYMOAB=OFF
cd bld
make
make check
make install

J

I actually tried this out today and I had the problem by I was able to compile MOAB by switching to version 5.2.0. There seems to be a bug in v5.1.0.

J