# Undefined symbol when run my CLI modules extensions

**URL:** <https://discourse.slicer.org/t/undefined-symbol-when-run-my-cli-modules-extensions/2393>\
**Category:** Development\
**Created:** [March 21, 2018, 9:06pm UTC](https://discourse.slicer.org/t/undefined-symbol-when-run-my-cli-modules-extensions/2393 "2018-03-21T21:06:46Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [March 29, 2018, 5:38am UTC](https://discourse.slicer.org/t/undefined-symbol-when-run-my-cli-modules-extensions/2393/14 "2018-03-29T05:38:05Z")

</div>

> one has the date in the second line while the other has not

This is normal, to build a release that do not include the date, you would have to set the option `-DSlicer_RELEASE_TYPE:STRING=Stable`. See [ReleaseProcess](https://www.slicer.org/wiki/Documentation/Nightly/Developers/ReleaseProcess#Day_1:_Release) checklist.

But the impact is only cosmetic.

> If anyone was able to build a compatible Slicer

You can **not** build extension using Ubuntu 16.04 and expect them to be compatible with the Slicer 4.8.1 release.

Indeed, the Slicer 4.8.1 release was done using Ubuntu 10.04.

Considering it is not possible to install such an old distribution, there is we now docker images allowing to reproduce builds.

Following this guide will allow you to build your extension and have it working with the Slicer 4.8.1 Linux release.

See [Introducing SlicerBuildEnvironment project](https://discourse.slicer.org/t/introducing-slicerbuildenvironment-project/2465#heading--step-by-step-1)

---

_[View the full topic](https://discourse.slicer.org/t/undefined-symbol-when-run-my-cli-modules-extensions/2393)._