[MacPorts] #61987: gobject-introspection @1.60.2_4 : g-ir-scanner producing executable with linking problems

[MacPorts]

#61987: gobject-introspection @1.60.2_4 : g-ir-scanner producing executable with
linking problems
------------------------------------+----------------------
  Reporter:  serge-cohen            |      Owner:  mascguy
      Type:  defect                 |     Status:  reopened
  Priority:  Normal                 |  Milestone:
 Component:  ports                  |    Version:  2.6.4
Resolution:                         |   Keywords:
      Port:  gobject-introspection  |
------------------------------------+----------------------

Comment (by ryandesign):

 Replying to [comment:16 dkossack]:
 > Is there something here that I am missing, that will fix the issue?

 If a fix were known, it would be in the port and the ticket would be
 closed.

 Replying to [comment:23 dkossack]:
 > The trace mode was at the request of mascguy (Christopher Nielsen)
 earlier in the thread... The symlink has been working ok, in the past
 there were some breaks but I have straightened out most of the issues at
 this point. I don't think this is the problem.

 Ok, well, evidently trace mode doesn't work when the MacPorts prefix has
 been replaced with a symlink, at least not with this port, so let's stop
 trying to use trace mode now.

 > What really changed between gexiv2 0.14.2 and gexiv2 0.14.3 ??

 Per [9cac4f2540a9aa366fdc2142973c58b2600da110/macports-ports], nothing
 changed with the port other than the version update.

 The changes listed for 0.14.3 in
 [https://gitlab.gnome.org/GNOME/gexiv2/-/blob/gexiv2-0.14.3/NEWS gexiv2's
 NEWS file] don't sound relevant to this issue.

 > I looked for a copy of gexiv2 0.14.2 to reinstall so I can get
 GIMP2.10.38 working again but I didn't come up with anything.

 You can try wiki:howto/InstallingOlderPort however it's by no means
 certain that the gexiv2 0.14.3 update is what causes the problem to
 happen; it could instead be an update to one of its dependencies, for
 example. Or it could be, as Chris suggested, interference from other
 installed ports that are not dependencies which, using trace mode, if it
 worked, would rule out.

 > Am I the only one having this issue??

 At least the person who reported this ticket four years ago experienced
 the issue, and the other people who filed duplicate bug reports since
 then, and per [comment:9 earlier comments] there were several other
 similar tickets that we thought we had fixed but evidently haven't.

 No gobject-introspection developer has ever responded to
 [https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues/335 the bug
 report I filed four years ago] so they obviously don't care that their
 software doesn't work.

-- 
Ticket URL: <https://trac.macports.org/ticket/61987#comment:24>
MacPorts <https://www.macports.org/>
Ports system for macOS