# Building for Ubuntu 16.04 LTS in CI

**URL:** <https://forum.graphviz.org/t/building-for-ubuntu-16-04-lts-in-ci/167>\
**Category:** Dev\
**Created:** [June 5, 2020, 4:08pm UTC](https://forum.graphviz.org/t/building-for-ubuntu-16-04-lts-in-ci/167 "2020-06-05T16:08:49Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![magjac](https://sea2.discourse-cdn.com/graphviz/user_avatar/forum.graphviz.org/magjac/32/16_2.png) [@magjac](https://forum.graphviz.org/u/magjac)\
**Post date:** [June 6, 2020, 8:27am UTC](https://forum.graphviz.org/t/building-for-ubuntu-16-04-lts-in-ci/167/6 "2020-06-06T08:27:20Z")

</div>

Those issues are the same as I encountered and led up to the Docker file for Ubuntu 16.04 that I posted above, even though `libltdl-dev` was implicitly included by something else, so I didn’t have that problem.

This again raises the question [how our build system is supposed to work](https://forum.graphviz.org/t/requesting-new-docker-images-with-ghostscript/150/11). I would’ve expected that it shouldn’t complain about missing things that it has already detected it cannot build.

> [@Ellson](#):
>
> The ./configure is in debian/rules, so somehow these rules should be modified for different versions of Ubuntu

My expectation would be that this was done automatically per above, not that a hack for each operating system should be necessary. That could also have negative consequences. Suppose a user has an Ubuntu 16.04 system with `ocaml` included, they would be prohibited to build with `ocaml` by the rule modification you suggest.

Sorry if I have misunderstood something. In that case, please educate me.

---

_[View the full topic](https://forum.graphviz.org/t/building-for-ubuntu-16-04-lts-in-ci/167)._