Alexey Sheplyakov

> That is, if there are no problems with absolute paths or similar. Actually there are two path related problems. 1. Absolute paths to sources and "system" headers in `.d`...

> @asheplyakov hi > > Does a comment by @ploxiln - [#1155 (comment)](https://github.com/libevent/libevent/issues/1155#issuecomment-1554645836) resolves you problem? Nope. My application uses libevent indirectly (via Qt and libldap). Patching and rebuilding Qt...

> This is a compiler bug, not darktable’s. But probably it’s a good idea to add some kind of workaround. To be more specific this looks like [GCC bug 96341](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96341),...

> The [workaround](https://salsa.debian.org/debian-phototools-team/darktable/-/commit/cda1ef8a8bd8e1fd6f73ae290f5edf42766f041d) is to build w/ `-DUSE_OPENMP=OFF` on arm64 when using GCC for now. Alternatively one can disable `stack-protector-strong` (Debian GCC [sets it by default](https://salsa.debian.org/toolchain-team/gcc/-/blob/gcc-13-debian/debian/patches/gcc-distro-specs.diff#L36)).

>> You need to install the packages in requirements.txt to get the importlib-resources compatibility package.  I've tried that (via pip install -r requirements.txt), the application failed to start anyway. I...

> > `python3 setup.py install` installs importlib-resources as a dep as expected ... Yes. But it skips share and stock_configs (unless there is the `__init__.py` file in the directory) >...

> > Yes. But it skips share and stock_configs (unless there is the `__init__.py` file in the directory) > > If that was the case, I would not have had...

CI jobs are failing since `MarkupSafe==1.0` fails to install with `setuptools