Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#62432 closed defect (fixed)

links @2.2.1+x11: configure: error: No graphics drivers found

Reported by: mcjsk (Mark Jamsek) Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: ports Version: 2.6.4
Keywords: Cc:
Port: links

Description

Platform

macOS Catalina Version 10.15.7 (19H524)
Darwin Kernel Version 19.6.0: Tue Jan 12 22:13:05 PST 2021; root:xnu-6153.141.16~1/RELEASE_X86_64 x86_64
Xcode 12.4 Build version 12D4e

Summary

sudo port upgrade fails when trying to upgrade port links with a configure error (see attached logs)

Reproduce

√ ~ → port outdated
The following installed ports are outdated:
gd2                            2.3.1_0 < 2.3.2_0
 √ ~ → sudo port clean links
--->  Cleaning links
 √ ~ → sudo port upgrade outdated
--->  Computing dependencies for links
--->  Fetching archive for links
--->  Attempting to fetch links-2.21_0+x11.darwin_19.x86_64.tbz2 from https://lil.fr.packages.macports.org/links
--->  Attempting to fetch links-2.21_0+x11.darwin_19.x86_64.tbz2 from https://mse.uk.packages.macports.org/links
--->  Attempting to fetch links-2.21_0+x11.darwin_19.x86_64.tbz2 from https://packages.macports.org/links
--->  Fetching distfiles for links
--->  Verifying checksums for links
--->  Extracting links
--->  Configuring links
Error: Failed to configure links, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_www_links/links/work/links-2.21/config.log
Error: Failed to configure links: configure failure: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_www_links/links/main.log for details.
Error: Problem while installing links
Error: Follow https://guide.macports.org/#project.tickets to report a bug.

Strangely, links is not a requested port, gd2 is a dependency of the requested port graphviz but doesn't appear to depend on links, and I can't determine which port recursively depends on it either, so I don't know why sudo port upgrade outdated is even attempting to configure links.

Attachments (2)

config.log (171.3 KB) - added by mcjsk (Mark Jamsek) 3 years ago.
main.log (52.5 KB) - added by mcjsk (Mark Jamsek) 3 years ago.

Download all attachments as: .zip

Change History (12)

Changed 3 years ago by mcjsk (Mark Jamsek)

Attachment: config.log added

Changed 3 years ago by mcjsk (Mark Jamsek)

Attachment: main.log added

comment:1 in reply to:  description ; Changed 3 years ago by jmroot (Joshua Root)

Strangely, links is not a requested port, gd2 is a dependency of the requested port graphviz but doesn't appear to depend on links, and I can't determine which port recursively depends on it either, so I don't know why sudo port upgrade outdated is even attempting to configure links.

gd2 -> libheif -> gdk-pixbuf2 -> shared-mime-info -> xmlto -> links

The config.log has a bunch of implicit declaration errors, very common since Xcode 12 became more strict about this.

comment:2 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: nobody removed
Keywords: x86_64 removed
Summary: links @2.2.1+x11: configure error – build failurelinks @2.2.1+x11: configure: error: No graphics drivers found

A bit silly that gd2 ends up depending on links. Oh well.

Unsurprisingly, it is not valid to Cc "nobody".

comment:3 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)

Owner: set to ryandesign
Resolution: fixed
Status: newclosed

In 6b6a5ebf0b6106c472d0d472fa2603d47d65a81d/macports-ports (master):

links: Fix implicit declaration of functions

Closes: #62432

comment:4 in reply to:  1 Changed 3 years ago by mcjsk (Mark Jamsek)

Replying to jmroot:

gd2 -> libheif -> gdk-pixbuf2 -> shared-mime-info -> xmlto -> links

Thanks, Joshua. For future reference, how did you determine this? I used {r}dependents and echo depends:, and tried tracing its dependencies through https://ports.macports.org/port/gd2 but must have overlooked it.

comment:5 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)

You'll note that the ports web page entry for gd2 doesn't list libheif, because the ports web site is not currently importing new information due to a bug; see #62401.

I don't know of a quick command to generate the information you want. I've often wanted to make one, but that kind of thing is not especially my area of expertise.

comment:6 in reply to:  2 Changed 3 years ago by mcjsk (Mark Jamsek)

Replying to ryandesign:

A bit silly that gd2 ends up depending on links. Oh well.

Unsurprisingly, it is not valid to Cc "nobody".

I debated it, but nobody was listed as the owner and I presumed it might be aliased to someone so went with it. I won't do that again.

And thank you. It's working now, much appreciated.

comment:7 in reply to:  5 Changed 3 years ago by mcjsk (Mark Jamsek)

Replying to ryandesign:

I don't know of a quick command to generate the information you want. I've often wanted to make one, but that kind of thing is not especially my area of expertise.

It would be a nice command to have; if time permits I'll look into what's involved to implement it but my plate is full for awhile. Also, I just had a look at the codebase and tcl is foreign to me so definitely not my area of expertise either.

comment:8 in reply to:  5 Changed 3 years ago by mcjsk (Mark Jamsek)

Replying to ryandesign:

I don't know of a quick command to generate the information you want. I've often wanted to make one, but that kind of thing is not especially my area of expertise.

Actually, come to think of it, would -y already provide this feature? For example, in this instance would port -y upgrade gd2 have revealed recursive dependencies?

comment:9 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)

Try it out. I don't think it's going to print any info about ports in the chain that are not outdated.

comment:10 in reply to:  9 Changed 3 years ago by mcjsk (Mark Jamsek)

Replying to ryandesign:

Try it out. I don't think it's going to print any info about ports in the chain that are not outdated.

I did before commenting and, as you suspect, it didn't output anything as my ports are up-to-date. I'll have to try again before my weekly launchd agent upgrades any outdated ports. I'll provide an update here when I do.

Note: See TracTickets for help on using tickets.