# Build Failure Suse Enterprise 12

**URL:** <https://discourse.slicer.org/t/build-failure-suse-enterprise-12/7752>\
**Category:** Development\
**Created:** [July 25, 2019, 12:37pm UTC](https://discourse.slicer.org/t/build-failure-suse-enterprise-12/7752 "2019-07-25T12:37:39Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [July 25, 2019, 1:56pm UTC](https://discourse.slicer.org/t/build-failure-suse-enterprise-12/7752/4 "2019-07-25T13:56:26Z")

</div>

I haven’t used it myself, but apparently Singularity helps get around some of these cross-linux dependency issues. [It’s apparently able to be used with Slicer](https://discourse.slicer.org/t/error-when-run-3dslicer-in-singularity-container/7599). Probably still requires some help from the cluster sysadmins if you want to install it.

But getting back to the build error, I’m not sure why qMRMLWidgetsCxxTests would be built if testing is turned off. In any case the Slicer app code should not depend on it, so maybe you can do `make -k` to build everything and just ignore the failing build of the test (or maybe you’ll get a similar link error on the app level - this looks like a qt issue - you might also try turning off `Slicer_BUILD_WEBENGINE_SUPPORT`).

---

_[View the full topic](https://discourse.slicer.org/t/build-failure-suse-enterprise-12/7752)._