Strange error when building GEGL from source: undefined symbol: gegl_node_connect

Fresh pull, commit 8018e6bd.

meson build seems OK.

During ninja build:

[1321/1324] Generating docs/website/operations/images/doc-operations-img with a custom command
/Gimp-dev/2.99/build/gegl/_build/tools/gegl-tester: symbol lookup error: /Gimp-dev/2.99/build/gegl/_build/tools/gegl-tester: undefined symbol: gegl_node_connect
[1321/1324] Generating docs/website/class_hierarchy_html with a custom command (wrapped by meson to capture output)
FAILED: docs/website/operations/images/gegl-oilify.png 
/usr/bin/env GEGL_SWAP=/Gimp-dev/2.99/build/gegl/_build/RAM GEGL_PATH=/Gimp-dev/2.99/build/gegl/_build/operations BABL_TOLERANCE=0.0 /Gimp-dev/2.99/build/gegl/_build/tools/gegl-tester --data-directory /Gimp-dev/2.99/build/gegl/docs/images --output-directory docs/website/operations/images --all --exclusion-pattern 'gegl:buffer-source|gegl:exr-load|gegl:ff-load|gegl:gegl-buffer-load|gegl:gif-load|gegl:icc-load|gegl:jp2-load|gegl:jpg-load|gegl:load|gegl:magick-load|gegl:open-buffer|gegl:pdf-load|gegl:pixbuf|gegl:png-load|gegl:ppm-load|gegl:rawbayer-load|gegl:raw-load|gegl:rgbe-load|gegl:svg-load|gegl:tiff-load|gegl:v4l|gegl:v4l2|gegl:webp-load|gegl:buffer-sink|gegl:display|gegl:exr-save|gegl:ff-save|gegl:gegl-buffer-save|gegl:icc-save|gegl:jpg-save|gegl:npy-save|gegl:png-save|gegl:ppm-save|gegl:rgbe-save|gegl:save|gegl:save-pixbuf|gegl:sdl2-display|gegl:tiff-save|gegl:webp-save|gegl:write-buffer|gegl:cache|gegl:cast-format|gegl:clone|gegl:convert-format|gegl:copy-buffer|gegl:image-compare|gegl:line-profile|gegl:nop|gegl:exp-combine|gegl:gegl|gegl:introspect|gegl:lcms-from-profile|gegl:mblur|gegl:alpha-inpaint|gegl:integral-image|gegl:aces-rrt'
[1323/1324] Generating docs/website/class_hierarchy_html with a custom command (wrapped by meson to capture output)
ninja: build stopped: subcommand failed.

Not a single idea where to look. Anyone?

check LD_LIBRARY_PATH is right in case the wrong gegl library is found at runtime?

So it appears that “the wrong library” is whatever was installed in an old failed build (december 2022). Cleaning that out fixed the problem. Thx.

This topic was automatically closed 45 days after the last reply. New replies are no longer allowed.