[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 mascguy):

 Replying to [comment:18 dkossack]:
 > Replying to [comment:17 mascguy]:
 > > This is a long shot, but... can you provide the output of `otool -L
 /opt/local/lib/libexiv2.dylib`?
 >
 > {{{
 > root# otool -L /opt/local/lib/libexiv2.dylib
 > /opt/local/lib/libexiv2.dylib:
 >       /Volumes/PEluard/opt/local/lib/libexiv2.27.dylib (compatibility
 version 27.0.0, current version 0.27.6)
 >       /Volumes/PEluard/opt/local/lib/libexpat.1.dylib (compatibility
 version 10.0.0, current version 10.10.0)
 >       /Volumes/PEluard/opt/local/lib/libz.1.dylib (compatibility version
 1.0.0, current version 1.2.13)
 >       /Volumes/PEluard/opt/local/lib/libiconv.2.dylib (compatibility
 version 9.0.0, current version 9.1.0)
 >       /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current
 version 902.1.0)
 >       /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
 version 1281.100.1)
 > }}}
 >
 > > Another idea, can you run `sudo port clean gexiv2` followed by `sudo
 port -t install gexiv2`? (I doubt this will help, but just throwing out
 ideas.) Assuming it fails, attach the `main.log`.
 >
 > {{{
 > root# port clean gexiv2
 > --->  Cleaning gexiv2
 >
 > root# port -t install gexiv2
 > --->  Computing dependencies for gexiv2
 > --->  Fetching distfiles for gexiv2
 > --->  Verifying checksums for gexiv2
 > --->  Extracting gexiv2
 > Warning: The following existing file was hidden from the build system by
 trace mode:
 >   /private/var/select/sh
 > Warning: The following file inside the MacPorts prefix not installed by
 a port was accessed:
 >   /Volumes/PEluard/opt/local/bin/xz
 > --->  Applying patches to gexiv2
 > Warning: The following existing file was hidden from the build system by
 trace mode:
 >   /private/var/select/sh
 > --->  Configuring gexiv2
 > Warning: The following existing files were hidden from the build system
 by trace mode:
 >   /opt/local/bin/meson-3.12
 >   /private/var/select/sh
 > Warning: The following file inside the MacPorts prefix not installed by
 a port was accessed:
 >   /Volumes/PEluard/opt/local/bin/meson
 > }}}

 From your latest `main.log`, the following failure occurs:

 {{{
 :info:configure sh: /Volumes/PEluard/opt/local/bin/meson: No such file or
 directory
 }}}

 Which doesn't make any sense, as that almost suggests that Meson isn't
 installed. But it is based on the earlier entries in the log.

 A related warning is this:

 {{{
 > Warning: The following existing files were hidden from the build system
 by trace mode:
 >   /opt/local/bin/meson-3.12
 }}}

 Assuming you installed MacPorts from scratch, via your custom prefix
 (`/Volumes/PEluard/opt/local`), all MacPorts-related paths should be
 prefixed with that. But the fact that `/opt/local` also exists, suggests
 something more is going on.

 Is `/opt/local` a symlink to `/Volumes/PEluard/opt/local`? Or do you have
 another MacPorts setup installed in `/opt/local`?

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