[MacPorts] #74194: glib2 fails to upgrade on Mac OS10.15
MacPorts
noreply at macports.org
Mon Jul 20 09:30:05 UTC 2026
#74194: glib2 fails to upgrade on Mac OS10.15
------------------------+----------------------
Reporter: lpagani91 | Owner: mascguy
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.12.5
Resolution: | Keywords:
Port: glib2 |
------------------------+----------------------
Comment (by isolated-matrix):
Replying to [comment:8 reneeotten]:
> okay, so you have stuff installed outside of MacPorts (and Homebrew) as
none of these install stuff in `/usr/local/*` - that is something you will
have to resolve before anyone (or at least me) will do anything about this
ticket. You will need to show that this is an issue on a clean system.
It looks like the stuff I have in those directories are libraries from
other programs. I have installed gfortran from the HPC MacOS website
(because I couldn't figure out how to get gfortran from macports), but
everything else looks quite harmless. Do you know which file is confusing
macports?
> I guess it's possible that if the {{{.so}}} files from {{{glib-
networking}}} were compiled against a different, already-installed
GLib/GIO ABI it could cause such a build failure. Can you try do
(temporarily) deactivate the {{{glib-networking}}} port and see if that
fixes the failure. That at least would give possibly an actionable thing
to try and fix in the sense that it is a MacPorts issue then and not
related to stuff you have installed outside of the package manager.
Unfortunately, that didn't help.
This is definitely a MacPorts issue, and not related to my system. All
these issues only popped up after the MacPorts update earlier this year. I
installed gfortran well over a year ago, but the first time I have ever
had to deal with broken ports like this was following that update. It
could be the case that I need to do a fresh installation of MacPorts, but
I'd rather avoid that if possible... My copy of gfortran also happens to
be outdated, so if you think that's really the root of the problem I could
try updating that, too.
--
Ticket URL: <https://trac.macports.org/ticket/74194#comment:9>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list