# Build fails in vtkExodus on Linux

**URL:** <https://discourse.slicer.org/t/build-fails-in-vtkexodus-on-linux/12018>\
**Category:** Development\
**Tags:** build\
**Created:** [June 14, 2020, 12:42pm UTC](https://discourse.slicer.org/t/build-fails-in-vtkexodus-on-linux/12018 "2020-06-14T12:42:35Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![chir.set](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/chir.set/32/66982_2.png) [@chir.set](https://discourse.slicer.org/u/chir.set)\
**Post date:** [June 22, 2020, 5:46pm UTC](https://discourse.slicer.org/t/build-fails-in-vtkexodus-on-linux/12018/14 "2020-06-22T17:46:54Z")

</div>

Amongst the many [changes](https://gcc.gnu.org/gcc-10/changes.html) in GCC 10, the use of -fno-common by default explains this behaviour. The fix is therefore valid, moreover explained [here](https://wiki.gentoo.org/wiki/Gcc_10_porting_notes/fno_common); except that I don’t know the effect of the ‘tags’ change in the patch.

I am seeing linking issues with GCC 10, despite the patch now, reported [here](https://discourse.slicer.org/t/build-fails-in-vtk-many-undefined-references/12150). Going with clang for now.

---

_[View the full topic](https://discourse.slicer.org/t/build-fails-in-vtkexodus-on-linux/12018)._