[MacPorts] #73754: pandoc @3.9.0.2_0: fails to build if gcc is installed

[MacPorts]

#73754: pandoc @3.9.0.2_0: fails to build if gcc is installed
---------------------+--------------------
  Reporter:  mark4o  |      Owner:  judaew
      Type:  defect  |     Status:  closed
  Priority:  Normal  |  Milestone:
 Component:  ports   |    Version:  2.12.4
Resolution:  fixed   |   Keywords:
      Port:  pandoc  |
---------------------+--------------------
Changes (by pmetzger):

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


Comment:

 In [changeset:"847649d272216b580a0a5c87b76d282d31e78367/macports-ports"
 847649d272216b580a0a5c87b76d282d31e78367/macports-ports] (master):
 {{{
 #!ConfigurableCommitTicketReference repository="macports-ports"
 revision="847649d272216b580a0a5c87b76d282d31e78367"
 pandoc: use selected clang for Cabal builds on Darwin

 On newer Darwin releases, pandoc is built from source using Cabal. If
 the selected MacPorts compiler is a gcc port, Cabal/GHC can end up
 using that compiler driver even though the MacPorts build environment
 and GHC's Darwin toolchain expect clang-compatible behavior. This
 breaks the pandoc build when clang-specific flags are passed to gcc.

 Blacklist gcc for Darwin source builds so MacPorts selects clang, and
 write Cabal program-default-options that pass -pgmc=${configure.cc} to
 both ghc and runghc. This makes Cabal's GHC invocations use the same
 compiler selected by MacPorts instead of inheriting an incompatible gcc
 from the user's environment.

 Also avoid applying Cabal-specific test arguments when building with
 the +stack variant.

 Closes: https://trac.macports.org/ticket/73754
 }}}

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