Opened 11 months ago

Closed 10 months ago

Last modified 10 months ago

#68968 closed defect (invalid)

graphviz-gui @9.0.0_0 unable to build on MacOS Sonoma

Reported by: edwardmoon (Edward Moon) Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: mascguy (Christopher Nielsen)
Port: graphviz-gui

Description (last modified by jmroot (Joshua Root))

Running Mac OS Sonoma 14.2.1 on a Mac Book Pro (M3 Pro cpu).

I was able to build and install graphviz but get errors trying to build graphviz-gui.

Output of port command:

-> % sudo port install graphviz-gui
Password:
--->  Computing dependencies for graphviz-gui
--->  Fetching archive for graphviz-gui
--->  Attempting to fetch graphviz-gui-9.0.0_0.darwin_23.arm64.tbz2 from https://packages.macports.org/graphviz-gui
--->  Attempting to fetch graphviz-gui-9.0.0_0.darwin_23.arm64.tbz2 from http://mirror.fcix.net/macports/packages/graphviz-gui
--->  Attempting to fetch graphviz-gui-9.0.0_0.darwin_23.arm64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/graphviz-gui
--->  Fetching distfiles for graphviz-gui
--->  Verifying checksums for graphviz-gui
--->  Extracting graphviz-gui
--->  Applying patches to graphviz-gui
--->  Configuring graphviz-gui
--->  Building graphviz-gui
Error: Failed to build graphviz-gui: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_graphviz/graphviz-gui/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
Error: Processing of port graphviz-gui failed

Attached main.log to ticket

Attachments (1)

main.log (349.0 KB) - added by edwardmoon (Edward Moon) 11 months ago.
main.log file from graphviz-gui build

Download all attachments as: .zip

Change History (5)

Changed 11 months ago by edwardmoon (Edward Moon)

Attachment: main.log added

main.log file from graphviz-gui build

comment:1 Changed 11 months ago by edwardmoon (Edward Moon)

Description: modified (diff)

comment:2 Changed 11 months ago by jmroot (Joshua Root)

Cc: mascguy added
Description: modified (diff)
Owner: set to ryandesign
Port: graphviz-gui added
Status: newassigned
:info:build A required plugin failed to load. Please ensure system content is up-to-date — try running 'xcodebuild -runFirstLaunch'.

Please try that command.

comment:3 Changed 10 months ago by edwardmoon (Edward Moon)

Sorry for the late reply.

It looks like the xcodebuild command fixed the issue:

em@Sugarbee [18:39:48] [~]
-> % xcodebuild -runFirstLaunch
Install Started
1%.........20.........40.........60.........80......Install Succeeded
em@Sugarbee [18:19:44] [~]
-> % sudo port upgrade outdated
Password:
Nothing to upgrade.
--->  Scanning binaries for linking errors
--->  No broken files found.
--->  No broken ports found.
em@Sugarbee [18:20:38] [~]
-> % sudo port install graphviz-gui
--->  Computing dependencies for graphviz-gui
--->  Fetching archive for graphviz-gui
--->  Attempting to fetch graphviz-gui-9.0.0_0.darwin_23.arm64.tbz2 from https://packages.macports.org/graphviz-gui
--->  Attempting to fetch graphviz-gui-9.0.0_0.darwin_23.arm64.tbz2 from http://mirror.fcix.net/macports/packages/graphviz-gui
--->  Attempting to fetch graphviz-gui-9.0.0_0.darwin_23.arm64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/graphviz-gui
--->  Building graphviz-gui
--->  Staging graphviz-gui into destroot
--->  Installing graphviz-gui @9.0.0_0
--->  Activating graphviz-gui @9.0.0_0
--->  Cleaning graphviz-gui
--->  Scanning binaries for linking errors
--->  No broken files found.
--->  No broken ports found.
Last edited 10 months ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)

comment:4 Changed 10 months ago by kencu (Ken)

Resolution: invalid
Status: assignedclosed

excellent.

Indeed, building software has many moving parts, and having MacPorts test for each thing to be correctly set up has turned out to be difficult.

If you can think up a test for this issue to add to "port diagnose" that would be great.

Note: See TracTickets for help on using tickets.