Starting January 28th I've been unable to build gimp-app. My build system is amd64 running 14.3-RELEASE-p8. I believe my options are default (gimp has PRINT off). I get similar errors when I try to build with poudriere under 13.5-RELEASE. I tried looking for these problems with port fallout but don't see any build failures for gimp-app since December. My guess is that one of the gimp-app dependencies has non-default options and was updated between January 27th and 28th (my build server runs once a day). But given the large number of dependencies I don't see any easy ways to test this theory. mkdir -p `dirname scalable/go-bottom.svg` && ../../tools/svg-contrast ../Symbolic/scalable/go-bottom.svg scalable/go-bottom.svg 1.5 mkdir -p `dirname scalable/go-down.svg` && ../../tools/svg-contrast ../Symbolic/scalable/go-down.svg scalable/go-down.svg 1.5 sh: gdb: not found mkdir -p `dirname scalable/go-first.svg` && ../../tools/svg-contrast ../Symbolic/scalable/go-first.svg scalable/go-first.svg 1.5 sh: gdb: not found mkdir -p `dirname scalable/go-home.svg` && ../../tools/svg-contrast ../Symbolic/scalable/go-home.svg scalable/go-home.svg 1.5 sh: gdb: not found sh: gdb: not found mkdir -p `dirname scalable/go-last.svg` && ../../tools/svg-contrast ../Symbolic/scalable/go-last.svg scalable/go-last.svg 1.5 sh: gdb: not found sh: gdb: not found mkdir -p `dirname scalable/go-next.svg` && ../../tools/svg-contrast ../Symbolic/scalable/go-next.svg scalable/go-next.svg 1.5 mkdir -p `dirname scalable/go-previous.svg` && ../../tools/svg-contrast ../Symbolic/scalable/go-previous.svg scalable/go-previous.svg 1.5 mkdir -p `dirname scalable/go-top.svg` && ../../tools/svg-contrast ../Symbolic/scalable/go-top.svg scalable/go-top.svg 1.5 mkdir -p `dirname scalable/go-up.svg` && ../../tools/svg-contrast ../Symbolic/scalable/go-up.svg scalable/go-up.svg 1.5 mkdir -p `dirname scalable/help-about.svg` && ../../tools/svg-contrast ../Symbolic/scalable/help-about.svg scalable/help-about.svg 1.5 gmake[3]: *** [Makefile:2450: 64/gimp-warning.png] Error 255 gmake[3]: *** Waiting for unfinished jobs.... gmake[3]: *** [Makefile:2450: 64/gimp-info.png] Error 255 gmake[3]: *** [Makefile:2450: 64/gimp-error.png] Error 255 gmake[3]: *** [Makefile:2450: 64/gimp-frame.png] Error 255 gmake[3]: *** [Makefile:2450: 64/gimp-texture.png] Error 255 gmake[3]: *** [Makefile:2450: 64/gimp-question.png] Error 255 gmake[3]: Leaving directory '/wrkdirs/usr/ports/graphics/gimp-app/work/gimp-2.10.38/icons/Symbolic-High-Contrast' gmake[2]: *** [Makefile:675: all-recursive] Error 1 gmake[2]: Leaving directory '/wrkdirs/usr/ports/graphics/gimp-app/work/gimp-2.10.38/icons' gmake[1]: *** [Makefile:867: all-recursive] Error 1 gmake[1]: Leaving directory '/wrkdirs/usr/ports/graphics/gimp-app/work/gimp-2.10.38' gmake: *** [Makefile:768: all] Error 2 ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make: stopped in /usr/ports/graphics/gimp-app
Craig, can you add gdb to the BUILD_DEPENDS locally and see what you get? It might be trying to debug the crashes of its own build tools and get backtraces, and that might give a hint which libraries are involved.
Try if the prior babl version helps; gimp3-app bombed out building in a bare system for me (not poudriere), FreeBSD 15.0-amd64, and I see this in the stderr, and below that I am posting the latest commit to babl which coincides with your failures. ------------------------------------------- If this is a build-time tool, you may ignore this message. Relocatable builds require the executable to be installed in bin/ or lib*/ unlike: /usr/ports/graphics/gimp3-app/work/gimp-3.0.8/_build/plug-ins/common/test-plug-ins/file-compressor/file-compressor If this is a build-time tool, you may ignore this message. ../babl/babl-internal.h:218 void babl_fatal(const char *, ...)() Failed to read /proc/self/maps: No such file or directory warning: 4 _wait4.S: No such file or directory warning: File "/usr/local/lib/libpython3.11.so.1.0-gdb.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load". /usr/ports/graphics/gimp3-app/work/gimp-3.0.8/_build/app/gimp-console-3.0: LibGimpBase-WARNING: gimp: gimp_wire_read(): unexpected EOF ../babl/babl-internal.h:218 void babl_fatal(const char *, ...)() Failed to read /proc/self/maps: No such file or directory warning: 4 _wait4.S: No such file or directory warning: File "/usr/local/lib/libpython3.11.so.1.0-gdb.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load". /usr/ports/graphics/gimp3-app/work/gimp-3.0.8/_build/app/gimp-console-3.0: LibGimpBase-WARNING: gimp: gimp_wire_read(): unexpected EOF ../babl/babl-internal.h:218 void babl_fatal(const char *, ...)() Failed to read /proc/self/maps: No such file or directory warning: 4 _wait4.S: No such file or directory warning: File "/usr/local/lib/libpython3.11.so.1.0-gdb.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load". /usr/ports/graphics/gimp3-app/work/gimp-3.0.8/_build/app/gimp-console-3.0: LibGimpBase-WARNING: gimp: gimp_wire_read(): unexpected EOF Relocatable builds require the executable to be installed in bin/ or lib*/ unlike: /usr/ports/graphics/gimp3-app/work/gimp-3.0.8/_build/plug-ins/imagemap/imagemap ----------------------------------------- commit 3a83e203c8b5343f81159c2f8bfd85024db8cd14 Author: Dima Panov <fluffy@FreeBSD.org> Date: Tue Jan 27 14:40:03 2026 +0300 x11/babl: update to 0.1.120 release (+) Changelog: https://gitlab.gnome.org/GNOME/babl/-/blob/master/NEWS?ref_type=heads#L6-10
mentioning babl because the logs mention babl_fatal().
also, upstream has at <https://gitlab.gnome.org/GNOME/babl/-/blob/master/NEWS?ref_type=heads#L6-10> 2026-01-28 babl-0.1.122 fix for startup crash due to mis-loading of x86_64-v4 on -v2 with some ports. ----------------------------- so everyone here looking at failed gimp-app or gimp3-app builds try with either an older or newer babl than 0.1.120, so we may be inheriting an upstream bug in babl. FreeBSD used to have 0.1.116 before 01.120, in context: commit 3a83e203c8b5343f81159c2f8bfd85024db8cd14 Author: Dima Panov <fluffy@FreeBSD.org> Date: Tue Jan 27 14:40:03 2026 +0300 x11/babl: update to 0.1.120 release (+) Changelog: https://gitlab.gnome.org/GNOME/babl/-/blob/master/NEWS?ref_type=heads#L6-10 commit f8094040c02cc2ea7a20b75ab60c9c66aaab2550 Author: Dima Panov <fluffy@FreeBSD.org> Date: Wed Oct 8 16:36:56 2025 +0300 x11/babl: update 0.1.116 release (+) Changelog: https://gitlab.gnome.org/GNOME/babl/-/blob/master/NEWS?ref_type=heads#L6-8
(In reply to Matthias Andree from comment #1) I didn't see a difference. But I did notice: Optional Features: [...] Detailed backtraces: no so I added LIB_DEPENDS=libbacktrace.so:devel/libbacktrace I think I'm getting a different error now. (process:14085): GEGL-CRITICAL **: 21:36:54.752: gegl_find_relocatable_exe: assertion 'file != NULL' failed mkdir -p `dirname scalable/edit-undo.svg` && ../../tools/svg-contrast ../Symbolic/scalable/edit-undo.svg scalable/edit-undo.svg 1.5 (process:14088): GEGL-CRITICAL **: 21:36:54.753: gegl_find_relocatable_exe: assertion 'file != NULL' failed (process:14090): GEGL-CRITICAL **: 21:36:54.753: gegl_find_relocatable_exe: assertion 'file != NULL' failed mkdir -p `dirname scalable/folder.svg` && ../../tools/svg-contrast ../Symbolic/scalable/folder.svg scalable/folder.svg 1.5 (process:14095): GEGL-CRITICAL **: 21:36:54.753: gegl_find_relocatable_exe: assertion 'file != NULL' failed mkdir -p `dirname scalable/folder-new.svg` && ../../tools/svg-contrast ../Symbolic/scalable/folder-new.svg scalable/folder-new.svg 1.5 ../babl/babl-internal.h:218 void babl_fatal(const char *, ...)() Failed to read /proc/self/maps: No such file or directory (process:14096): GEGL-CRITICAL **: 21:36:54.753: gegl_find_relocatable_exe: assertion 'file != NULL' failed mkdir -p `dirname scalable/format-indent-more.svg` && ../../tools/svg-contrast ../Symbolic/scalable/format-indent-more.svg scalable/format-indent-more.svg 1.5 ../babl/babl-internal.h:218 void babl_fatal(const char *, ...)() Failed to read /proc/self/maps: No such file or directory ../babl/babl-internal.h:218 void babl_fatal(const char *, ...)() Failed to read /proc/self/maps: No such file or directorymkdir -p `dirname scalable/format-justify-fill.svg` && ../../tools/svg-contrast ../Symbolic/scalable/format-justify-fill.svg scalable/format-justify-fill.svg 1.5 (process:14099): GEGL-CRITICAL **: 21:36:54.754: gegl_find_relocatable_exe: assertion 'file != NULL' failed ../babl/babl-internal.h:218 void babl_fatal(const char *, ...)() Failed to read /proc/self/maps: No such file or directory mkdir -p `dirname scalable/format-justify-center.svg` && ../../tools/svg-contrast ../Symbolic/scalable/format-justify-center.svg scalable/format-justify-center.svg 1.5 ../babl/babl-internal.h:218 void babl_fatal(const char *, ...)() Failed to read /proc/self/maps: No such file or directory mkdir -p `dirname scalable/format-justify-left.svg` && ../../tools/svg-contrast ../Symbolic/scalable/format-justify-left.svg scalable/format-justify-left.svg 1.5 mkdir -p `dirname scalable/format-justify-right.svg` && ../../tools/svg-contrast ../Symbolic/scalable/format-justify-right.svg scalable/format-justify-right.svg 1.5 ../babl/babl-internal.h:218 void babl_fatal(const char *, ...)() Failed to read /proc/self/maps: No such file or directorymkdir -p `dirname scalable/go-bottom.svg` && ../../tools/svg-contrast ../Symbolic/scalable/go-bottom.svg scalable/go-bottom.svg 1.5
(In reply to Matthias Andree from comment #4) I reverted babl to 0.1.116 (f8094040c02) and graphics/gimp-app builds. I see 0.1.120 and 0.1.122 are available but the NEWS section doesn't appear relevant to the gimp-app build issue. 2026-01-28 babl-0.1.122 </dt><dd> fix for startup crash due to mis-loading of x86_64-v4 on -v2 with some ports. </dd><dt> 2026-01-15 babl-0.1.120 </dt><dd> x86_64-v4 microarchitecture support.
I disabled relocatable support for now, apparently only Linux, Windows and macOS are currently supported. Once we have proper support, it will be enabled again, since some GEGL filters need it. *** This bug has been marked as a duplicate of bug 292859 ***
(In reply to Charlie Li from comment #7) I can confirm I can still build gimp-app-2.10.38_8,1 with babl-0.1.122. Thanks for the fix!