# Possible issue in vtkloguru with musl in 9.1.0

**URL:** <https://discourse.vtk.org/t/possible-issue-in-vtkloguru-with-musl-in-9-1-0/9526>\
**Category:** Development\
**Created:** [October 4, 2022, 4:20pm UTC](https://discourse.vtk.org/t/possible-issue-in-vtkloguru-with-musl-in-9-1-0/9526 "2022-10-04T16:20:27Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![waebbl](https://discourse.vtk.org/user_avatar/discourse.vtk.org/waebbl/32/5870_2.png) [@waebbl](https://discourse.vtk.org/u/waebbl)\
**Post date:** [October 4, 2022, 4:20pm UTC](https://discourse.vtk.org/t/possible-issue-in-vtkloguru-with-musl-in-9-1-0/9526/1 "2022-10-04T16:20:27Z")

</div>

Hello,

I received a bug report from a machine running musl when building vtkloguru module[1].

After looking into this, I noticed, there’s some logic in KWSys which handles missing `execinfo.h` properly. The build log attached at the bug report also shows, that the file is not found. Shouldn’t loguru.cpp use this info and check for the file before trying to #include it?

[1] [873601 – sci-libs/vtk-9.1.0-r2 fails to compile (MUSL): loguru.cpp:98:18: fatal error: execinfo.h: No such file or directory](https://bugs.gentoo.org/873601)

---

<div class="post-metadata">

**Author:** ![ben.boeckel](https://discourse.vtk.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.vtk.org/u/ben.boeckel)\
**Post date:** [October 4, 2022, 5:05pm UTC](https://discourse.vtk.org/t/possible-issue-in-vtkloguru-with-musl-in-9-1-0/9526/2 "2022-10-04T17:05:24Z")

</div>

How is [`loguru` upstream](https://github.com/emilk/loguru) handling musl support? Does Alpine carry patches that should be sent upstream?

---

<div class="post-metadata">

**Author:** ![waebbl](https://discourse.vtk.org/user_avatar/discourse.vtk.org/waebbl/32/5870_2.png) [@waebbl](https://discourse.vtk.org/u/waebbl)\
**Post date:** [October 4, 2022, 5:36pm UTC](https://discourse.vtk.org/t/possible-issue-in-vtkloguru-with-musl-in-9-1-0/9526/3 "2022-10-04T17:36:36Z")

</div>

Looks like upstream doesn’t handle musl. The code looks like the files in vtkloguru. I don’t know how Alpine handles patches, on Gentoo we don’t have the package available.

Upstream has an open issue for about 4 years on this[1] which isn’t yet resolved.

[1] [https://github.com/emilk/loguru/issues/69](https://github.com/emilk/loguru/issues/69)

---

<div class="post-metadata">

**Author:** ![ben.boeckel](https://discourse.vtk.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.vtk.org/u/ben.boeckel)\
**Post date:** [October 4, 2022, 7:04pm UTC](https://discourse.vtk.org/t/possible-issue-in-vtkloguru-with-musl-in-9-1-0/9526/4 "2022-10-04T19:04:28Z")

</div>

In that case, you can just set `VTK_ENABLE_LOGGING=OFF` (and `VTK_MODULE_ENABLE_VTK_loguru=NO` to ensure it) for `musl` builds in the meantime.

---

<div class="post-metadata">

**Author:** ![ben.boeckel](https://discourse.vtk.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.vtk.org/u/ben.boeckel)\
**Post date:** [October 4, 2022, 7:14pm UTC](https://discourse.vtk.org/t/possible-issue-in-vtkloguru-with-musl-in-9-1-0/9526/5 "2022-10-04T19:14:52Z")

</div>

I’ve subscribed to the issue at least and can cherry-pick whatever is accepted into our copy when that happens.

---

<div class="post-metadata">

**Author:** ![waebbl](https://discourse.vtk.org/user_avatar/discourse.vtk.org/waebbl/32/5870_2.png) [@waebbl](https://discourse.vtk.org/u/waebbl)\
**Post date:** [October 4, 2022, 8:41pm UTC](https://discourse.vtk.org/t/possible-issue-in-vtkloguru-with-musl-in-9-1-0/9526/6 "2022-10-04T20:41:42Z")

</div>

Thanks, that’s what I was planning to do