#63587 closed defect (fixed)
gimp2: Error: GIMP configuration failed
Reported by: | squiggledid | Owned by: | mascguy (Christopher Nielsen) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ||
Port: | gimp2 |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Port gimp2 fails during configuration on MacOS 10.14.6 with the error message:
---> Configuring gimp2 Error: Failed to configure gimp2: consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_gimp2/gimp2/work/gimp-2.10.28/config.log Error: Failed to configure gimp2: configure failure: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_gimp2/gimp2/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port gimp2 failed
I tried cleaning and trying again. Same result. I uninstalled and then tried installing again. Same result. I will attach the main.log and the config.log.
Attachments (2)
Change History (10)
Changed 3 years ago by squiggledid
comment:1 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|---|
Owner: | set to dbevans |
Status: | new → assigned |
Summary: | Port gimp2 fails during configuration on MacOS 10.14.6 → gimp2: Error: GIMP configuration failed |
The main.log says the problem is:
:info:configure Error: GIMP configuration failed. :info:configure - PyGTK 2.10.4 or newer :info:configure *** Please install it, or skip building the python scripting extension by :info:configure *** passing --disable-python to configure (but then you will not be able :info:configure *** to use scripts for GIMP that are written in Python). :info:configure See the file 'INSTALL' for more help.
The config.log explains further:
configure:34397: checking for pygtk-2.0 >= 2.10.4 configure:34404: $PKG_CONFIG --exists --print-errors "pygtk-2.0 >= 2.10.4" Variable 'PYTHON_EXEC_PREFIX' not defined in '/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/pkgconfig/pygtk-2.0.pc' configure:34407: $? = 1 configure:34421: $PKG_CONFIG --exists --print-errors "pygtk-2.0 >= 2.10.4" Variable 'PYTHON_EXEC_PREFIX' not defined in '/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/pkgconfig/pygtk-2.0.pc' configure:34424: $? = 1 configure:34438: result: no Variable 'PYTHON_EXEC_PREFIX' not defined in '/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/pkgconfig/pygtk-2.0.pc'
What happens if you run:
PKG_CONFIG_PATH=/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/pkgconfig pkg-config --exists --print-errors "pygtk-2.0 >= 2.10.4"; echo $?
On my system the result is
0
meaning no error, but I wonder if you get a different result. If so, maybe try forcibly uninstalling and then reinstalling py27-pygtk.
I also noted these errors in the main.log which probably also indicate something wrong:
:info:configure checking for matting engine Levin... GEGL-Message: 10:04:05.538: Module '/opt/local/lib/gegl-0.4/ff-save.dylib' load error: dlopen(/opt/local/lib/gegl-0.4/ff-save.dylib, 10): Library not loaded: @rpath/libgio-2.0.0.dylib :info:configure Referenced from: /opt/local/lib/libavcodec.58.dylib :info:configure Reason: image not found :info:configure GEGL-Message: 10:04:05.594: Module '/opt/local/lib/gegl-0.4/ff-load.dylib' load error: dlopen(/opt/local/lib/gegl-0.4/ff-load.dylib, 10): Library not loaded: @rpath/libgio-2.0.0.dylib :info:configure Referenced from: /opt/local/lib/libavcodec.58.dylib :info:configure Reason: image not found
(The use of @rpath seems wrong to me.)
comment:2 Changed 3 years ago by squiggledid
I tried what you suggested, and got this:
pkg-config --exists --print-errors "pygtk-2.0 >= 2.10.4"; echo $? Package pygtk-2.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `pygtk-2.0.pc' to the PKG_CONFIG_PATH environment variable No package 'pygtk-2.0' found 1
I then uninstalled and reinstalled py27-pygtk. I get the same result:
pkg-config --exists --print-errors "pygtk-2.0 >= 2.10.4"; echo $? Package pygtk-2.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `pygtk-2.0.pc' to the PKG_CONFIG_PATH environment variable No package 'pygtk-2.0' found 1
Yet it is indeed installed:
port installed | grep pygtk py27-pygtk @2.24.0_4+x11 (active)
So, has something broken broken the pkg-config search path? it is:
echo $PKG_CONFIG_PATH /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/pkgconfig
I don't know what it should be.
comment:3 Changed 3 years ago by mascguy (Christopher Nielsen)
Owner: | changed from dbevans to mascguy |
---|
comment:4 Changed 3 years ago by mascguy (Christopher Nielsen)
Both ports were updated late yesterday. Please rerun sudo port selfupdate
, and try the install again.
comment:5 Changed 3 years ago by mascguy (Christopher Nielsen)
Oh, be sure to re-run sudo port clean --all gimp2
first as well, before retrying the install.
comment:6 Changed 3 years ago by squiggledid
I'd already uninstalled and cleaned all my gimp2 versions.
I restarted the process as soon as I got your first message. The new update resulted in py27-pygtk @2.24.0_5+x11 being installed. gimp2 (gimp2-2.10.28_0+python27.darwin_18.x86_64) then configured successfully, and started building. It is now staging into destroot.
It would seem that the new gimp2 port was released before the new version of the py27-pygtk port on which it depended. This is not good.
comment:7 Changed 3 years ago by mascguy (Christopher Nielsen)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Great, glad it's working!
As for py27-pygtk: Despite a lot of exhaustive testing ahead of time, this issue was somehow missed. But thanks to two of my fellow members - who not only identified the issue, but but also provided the fix - we caught it quickly. You just happened to be bitten by it, before the fix was committed.
comment:8 Changed 3 years ago by squiggledid
The price of doing updates first thing in the morning in Australia, I guess :)
main.log from MacOS 10.14.6