Summary: | media-gfx/darktable: graphite handling needs improving | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sam James <sam> |
Component: | Current packages | Assignee: | Marek Szuba <marecki> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | jannik.glueckert, maekke, marecki, toolchain |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=695658 https://bugs.gentoo.org/show_bug.cgi?id=884057 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sam James
2024-02-22 06:37:44 UTC
1. Perhaps the comment you have quoted is not precise enough. However, it does NOT change the fact that when maekke and I got nagged about it last time, I tested what addingh BDEPEND="|| ( sys-devel/gcc[graphite] sys-devel/clang" to the ebuilds would do - and it resulted in Portage pulling in clang as a dependency of Mesa, followed by happily attempting to emerge darktable using non-Graphite gcc. Of course if you know how to solve this, you are very much welcome to let us know! 2. The commit in question removed Graphite requirement only from one bit of the code, there are still places where it is required. If you try emerging darktable yourself, you will see that versions up to and including 4.6.1 fail with sorry, unimplemented: Graphite loop optimizations cannot be used (isl is not available) when built using non-Graphite gcc. |