ninja: build stopped: subcommand failed. Error: Failed to build gegl: command execution failed

2023-01-12 Thread chilli.names...@gmail.com
What's strange is port outdated doesn't show anything, so I expect these ports are broken and my install doesn't know it. I bet it has something to do with port reclaim running when I tried to selfupdate. I deleted all the build directories out of habit. gegl @0.4.40_0+quartz+vala (active)

Re: GIMP Quartz broken on 10.7, perhaps gtk

2023-01-12 Thread Ken Cunningham
My guess would be to look at harfbuzz…make sure our patches there still make sense, run the test suite. It can be touchy, different compilers can change test results, etc. To disable one port in an overlay with minimal fuss, rename to Portfile to something else (I use Portfile.disabled), and

Re: GIMP Quartz broken on 10.7, perhaps gtk

2023-01-12 Thread Riccardo Mottola via macports-users
Hi! I did further tests here. In my local repository I pinned also a previous version of pango and pang-devel, but had difficulties "upgarding" to a previous version, how can it be done cleanly? Then I thought of just activating some previous versions… I had a bit mess here and there when

Re: GIMP Quartz broken on 10.7, perhaps gtk

2023-01-12 Thread Lukas Oberhuber
Riccardo, >> I see the same thing on a fresh gimp2 install +quartz on 10.7 (one very tiny >> patch needed to gimp2 to change NULL -> 0 to keep clang-15 happy, otherwise a >> no-touch build). > I have that too… I think Lukas can easily fix it. Or we can have in the meanwhile a small patch. It is

Re: GIMP Quartz broken on 10.7, perhaps gtk

2023-01-12 Thread Riccardo Mottola via macports-users
Hi, On 2023-01-08 23:24:55 +0100 Ken Cunningham wrote: > I see the same thing on a fresh gimp2 install +quartz on 10.7 (one very tiny > patch needed to gimp2 to change NULL -> 0 to keep clang-15 happy, otherwise a > no-touch build). I have that too… I think Lukas can easily fix it. Or we