[MacPorts] #61086: graphviz at 2.40.1_3+pangocairo+x11: /usr/lib//libiconv.la: No such file

[MacPorts]

#61086: graphviz at 2.40.1_3+pangocairo+x11: /usr/lib//libiconv.la: No such file
-----------------------+------------------------
  Reporter:  JDLH      |      Owner:  ryandesign
      Type:  defect    |     Status:  closed
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:  2.6.3
Resolution:  invalid   |   Keywords:
      Port:  graphviz  |
-----------------------+------------------------
Changes (by ryandesign):

 * status:  assigned => closed
 * resolution:   => invalid


Comment:

 Replying to [comment:5 JDLH]:
 > There is a `libgd.lai` in the mix also. I am not familiar with the
 `.lai` extension.

 I wasn't either. As far as I can tell in brief research, the .lai file
 would be created in the build directory, and then it would be copied to an
 .la file in the installation directory. In other words, an .lai file
 should never have been installed.

 > With that, `sudo port install graphviz` run successfully.  The
 workaround seems effective!

 Glad it worked!

 Replying to [comment:6 JDLH]:
 > Why are these very old, and unclaimed, libraries in `/opt/local/lib`?

 Only you can know that. :) One situation that we encounter from time to
 time is users who run third-party software installers that were themselves
 built using MacPorts set to its default prefix. Using such an installer
 would write files to the MacPorts prefix, overwriting files you might
 already have installed there using MacPorts and of course not informing
 MacPorts that this has happened. We advise people not to distribute
 installers that do this, but it happens. If you ran such an installer in
 2008 (or perhaps just an installer that was made in 2008) and gd2 was one
 of the things it installed, that could account for the presence of those
 files. And of course once they're there they're not going to be deleted
 unless you delete them; MacPorts isn't going to remove them for you since
 it didn't put them there and doesn't know they exist.

 I'm not sure why any .la file of any era would have referred to
 /usr/lib/libiconv.la on macOS since as far as I know macOS never shipped
 with any .la files in /usr/lib. So it's a bit of a mystery how you got
 that file.

 > I have upgraded macOS at least three times since 2008, and moved
 hardware at least twice. I followed the instructions for migrating
 MacPorts to the new OS. That includes listing the ports, uninstalling all
 of the ports, and reinstalling. However, it does not include deleting all
 of `/opt/local/*`.

 Right, deleting all of /opt/local is pretty disruptive, since you likely
 have files in there that you want to keep, such as configuration files,
 maybe databases, etc.

 > When migrating hardware, I use the Apple Migration Assistant, which
 probably copies all of `/opt/local/*` to the new machine.

 It does, if you ask it to. (I think you get the opportunity to say what
 information you want to transfer, right?)

 > Maybe I should delete the whole directory next time I migrate to a new
 macOS version.

 It might be a good idea. Whatever action put the gd2 .la file there could
 have installed other files as well that could cause problems in the
 future. But before you remove all of /opt/local, remember to save any
 config files or other files you modified and want to keep.

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