[MacPorts] #55137: source-highlight 3.1.8_0.darwin_15.x86_64: Undefined symbols for architecture x86_64

[MacPorts]

#55137: source-highlight 3.1.8_0.darwin_15.x86_64: Undefined symbols for
architecture x86_64
-------------------------------+------------------------
  Reporter:  hipunk            |      Owner:  ryandesign
      Type:  defect            |     Status:  closed
  Priority:  Normal            |  Milestone:
 Component:  ports             |    Version:  2.4.2
Resolution:  fixed             |   Keywords:
      Port:  source-highlight  |
-------------------------------+------------------------

Comment (by ryandesign):

 Replying to [comment:5 hipunk]:
 > Indeed, there is a /usr/local directory and it contains a boost library.
 > I assume it derives from having brew installed as well.

 Yes, that's a likely reason. This kind of problem is why we don't support
 having another package manager installed alongside MacPorts. It's best if
 you decide on one package manager to use and uninstall the other. Of
 course we'd love it if you chose MacPorts, and if there's anything we can
 do to help you choose MacPorts, let us know.

 > However, when I try to port using the -t flag, which apparently omits
 the /usr/local folders, the issue persists. I tried renaming /usr/local to
 /usr/localBAK, the issue persists.

 I agree that either using the `-t` flag or moving /usr/local aside should
 have been enough to work around this problem, provided in either case that
 you ran `sudo port clean source-highlight` first. (On El Capitan and
 later, System Integrity Protection will prevent you from moving
 /usr/local, so I assume you've turned SIP off.)

 > Hmm, do you have an idea how I could temporarily fix this? By exporting
 some $PATH or something?

 MacPorts deliberately does not honor your `PATH` environment variable, to
 prevent interference from non-MacPorts software you may have installed.
 Instead, MacPorts sets its `PATH` environment variable to the value of the
 `binpath` setting in macports.conf. It is not recommended to change this
 setting; its default value should work correctly.

 > I don't understand why it still fails when I rename /usr/local, so I'm
 out of ideas again. I understand, that I could modify the port in some way
 or another by using "--with-libfoo=/opt/local/lib/" (from the usrlocal
 FAQ), but I don't know where it expects its stuff to be in the first
 place...

 My [changeset:93f74d0a615e570c7a78fbf3415f8e3c309b6e9b/macports-ports
 commit shown above] added the `--with-boost=${prefix}` configure argument
 to the port, and should be enough to allow the port to find MacPorts
 boost, even if another boost is in /usr/local. Please `sudo port clean
 source-highlight`, then use `sudo port selfupdate` to receive that fix,
 then try installing the port again. If it fails again, please attach the
 new main.log (and the config.log in the work directory) so that we can see
 what else might be going on.

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