[MacPorts] #69274: lnav fails to install: error: invalid command-line arguments, reason: -i excludes -t

[MacPorts]

#69274: lnav fails to install: error: invalid command-line arguments, reason: -i
excludes -t
---------------------------+-------------------------
  Reporter:  barracuda156  |      Owner:  herbygillot
      Type:  defect        |     Status:  assigned
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.9.1
Resolution:                |   Keywords:
      Port:  lnav          |
---------------------------+-------------------------

Comment (by barracuda156):

 Replying to [comment:1 ryandesign]:
 > Probably upstream had good reason for using `CC_FOR_BUILD` instead of
 `CC` here so the fix is not to patch that but for the port to set
 `CC_FOR_BUILD` (and `CPPFLAGS_FOR_BUILD` and `LDFLAGS_FOR_BUILD` if any of
 those are necessary). Typically, the `*_FOR_BUILD` variables would be used
 for programs that are built to be run during the build by the build
 machine, as opposed to things being built to be installed and used on the
 end-user machine. If you believe upstream was incorrect to use the
 `*_FOR_BUILD` variables here, please share the upstream bug report URL or
 pull request or commit so we can check up on it.

 I certainly do not insist that usage of `CC_FOR_BUILD` is incorrect, but
 as a matter of fact upstream set-up as it exists now does not work.
 I actually tried to pass `CC_FOR_BUILD` via `build.env` initially, and it
 was ignored. What is the way to do it correctly?

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