Opened 14 months ago
Last modified 5 months ago
#68044 closed defect
Gimp configuration failure on a MacBook Pro 16 inch M1 - Ventura 13.5.1 — at Version 4
Reported by: | targetmarketphotography | Owned by: | mascguy (Christopher Nielsen) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.8.1 |
Keywords: | ventura arm64 | Cc: | |
Port: | gimp2 |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Failed to configure gimp2: consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_gimp2/gimp2/work/gimp-2.10.34/config.log Error: Failed to configure gimp2: configure failure: command execution failed
Change History (4)
comment:1 follow-up: 3 Changed 14 months ago by targetmarketphotography
comment:2 Changed 14 months ago by jmroot (Joshua Root)
Keywords: | configuration Ventura 13.5.1 Apple Silicone removed |
---|---|
Owner: | set to mascguy |
Port: | gimp2 added; Gimp removed |
Status: | new → assigned |
comment:3 Changed 14 months ago by mascguy (Christopher Nielsen)
Replying to targetmarketphotography:
contents of config.log -- NOT able to access the file to attach it
It's likely accessible, but config.log
may not be necessary. Instead, we need the port log, which you can access via port logfile gimp2
:
$ cp -v $(port logfile gimp2) gimp2-build-error.log
And please attach.
comment:4 Changed 14 months ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|
For configuration failures with autoconf-based software, both main.log and config.log should be attached. main.log tells you which configure test failed; config.log tells you why it failed.
Note: See
TracTickets for help on using
tickets.
contents of config.log -- NOT able to access the file to attach it