[ 17:08 Jean-Sébastien Pédron (dumbbell)  ]

• 229b2f86274a443876fdb8a9497109a18a459d66 graphics/darktable/Makefile
• 229b2f86274a443876fdb8a9497109a18a459d66 graphics/darktable/distinfo
• 229b2f86274a443876fdb8a9497109a18a459d66 graphics/darktable/files/patch-cmake_modules_FindOpenEXR.cmake
• 229b2f86274a443876fdb8a9497109a18a459d66 graphics/darktable/files/patch-src_CMakeLists.txt
• 229b2f86274a443876fdb8a9497109a18a459d66 graphics/darktable/files/patch-src_common_exif.cc
• 229b2f86274a443876fdb8a9497109a18a459d66 graphics/darktable/files/patch-src_common_iop__order.c
• 229b2f86274a443876fdb8a9497109a18a459d66 graphics/darktable/files/patch-src_common_iop__profile.c
• 229b2f86274a443876fdb8a9497109a18a459d66 graphics/darktable/files/patch-src_external_rawspeed_cmake_Modules_CheckZLIB.cmake
• 229b2f86274a443876fdb8a9497109a18a459d66 graphics/darktable/files/patch-src_iop_channelmixerrgb.c
• 229b2f86274a443876fdb8a9497109a18a459d66 graphics/darktable/files/patch-src_iop_filmicrgb.c

graphics/darktable: Update to 4.4.1

Release notes:
* https://github.com/darktable-org/darktable/releases/tag/release-4.4.0
* https://github.com/darktable-org/darktable/releases/tag/release-4.4.1

Support for MIDI devices is currently turned off even though it probably
works just fine. The port already has many options that make it
complicated enough. If there is demand for MIDI devices, I will add the
option.

[ 22:34 Jean-Sébastien Pédron (dumbbell)  ]

• 75ac7903573cdc224246b8ec9446a97e0e4c099d graphics/darktable/Makefile
• 75ac7903573cdc224246b8ec9446a97e0e4c099d graphics/darktable/files/patch-src_common_extra__optimizations.h
• 75ac7903573cdc224246b8ec9446a97e0e4c099d graphics/darktable/files/patch-src_common_iop__order.c
• 75ac7903573cdc224246b8ec9446a97e0e4c099d graphics/darktable/files/patch-src_common_iop__profile.c
• 75ac7903573cdc224246b8ec9446a97e0e4c099d graphics/darktable/files/patch-src_develop_blends_blendif__lab.c
• 75ac7903573cdc224246b8ec9446a97e0e4c099d graphics/darktable/files/patch-src_develop_blends_blendif__raw.c
• 75ac7903573cdc224246b8ec9446a97e0e4c099d graphics/darktable/files/patch-src_develop_blends_blendif__rgb__hsl.c
• 75ac7903573cdc224246b8ec9446a97e0e4c099d graphics/darktable/files/patch-src_develop_blends_blendif__rgb__jzczhz.c
• 75ac7903573cdc224246b8ec9446a97e0e4c099d graphics/darktable/files/patch-src_iop_channelmixerrgb.c
• 75ac7903573cdc224246b8ec9446a97e0e4c099d graphics/darktable/files/patch-src_iop_filmicrgb.c

graphics/darktable: Use GCC as the compiler instead of LLVM

Darktable source code is heavily tuned for GCC and its optimizations. It
always required some work to make it compile with LLVM. With LLVM 14+,
new errors around `static inline __attribute__((target-clones))`
appeared: the compiler failed to link the final executable because there
was multiple copies of the same ifunc resolver (the code originated from
a header included in a couple places). Apparently GCC knows how to deal
with the "static-inline"-ness of the resolver somehow.

Unfortunately, even with GCC, we get several compilation failures
because the source files enable Graphite optimizations (using `#pragma`)
but our GCC compiler has Graphite disabled by default. All the patches
included in this commit simply delete all the corresponding `#pragma`. I
suppose Darktable will be slightly slower because of this, but I didn't
measure anything.

In the end, the dependencies of the port change a bit because GCC
replaces LLVM.