[MacPorts] #59134: pdftk is using libstdc++ (this installation is configured to use libc++) (again)

[MacPorts]

#59134: pdftk is using libstdc++ (this installation is configured to use libc++)
(again)
-----------------------------+------------------------
  Reporter:  jacobakkerboom  |      Owner:  ryandesign
      Type:  defect          |     Status:  assigned
  Priority:  Normal          |  Milestone:
 Component:  ports           |    Version:
Resolution:                  |   Keywords:
      Port:  pdftk           |
-----------------------------+------------------------

Comment (by JDLH):

 I was able to work around this by editing the pdftk portfile as described
 by comment:5:issue:56554. That is, I removed `pdftk` with:
 {{{
 sudo port uninstall pdftk
 sudo port clean pdftk
 bbedit `port file pdftk`
 }}}

 Then I added a line after line 83 of `pdftk`'s Portfile. Old contents:
 {{{
 variant gcc5 conflicts gcc45 gcc47 description {Build using gcc5} {
     configure.compiler  macports-gcc-5
     set versuff         -mp-5
 }
 }}}
 New contents, with new line `configure.cxx_stdlib macports-libstdc++`:
 {{{
 variant gcc5 conflicts gcc45 gcc47 description {Build using gcc5} {
     configure.compiler  macports-gcc-5
     configure.cxx_stdlib macports-libstdc++
     set versuff         -mp-5
 }
 }}}

 Then I could install `pdftk` without any complaints about a broken port:
 {{{
 % sudo port install pdftk
 --->  Computing dependencies for pdftk
 --->  Fetching archive for pdftk
 --->  Attempting to fetch pdftk-2.02_0+gcc5.darwin_17.x86_64.tbz2 from
 https://packages.macports.org/pdftk
 --->  Attempting to fetch pdftk-2.02_0+gcc5.darwin_17.x86_64.tbz2.rmd160
 from https://packages.macports.org/pdftk
 --->  Installing pdftk @2.02_0+gcc5
 --->  Activating pdftk @2.02_0+gcc5
 --->  Cleaning pdftk
 --->  Updating database of binaries
 --->  Updating database of C++ stdlib usage
 --->  Scanning binaries for linking errors
 --->  No broken files found.
 --->  No broken ports found.
 }}}

 However, my understanding of comment:13:issue:56554 is that MacPorts from
 2.5.1 on should have done the equivalent of `configure.cxx_stdlib
 macports-libstdc++` without this statement in the Portfile. This makes me
 thing that the fix from MacPorts 2.5.1 is missing from 2.6.0 and 2.6.2, or
 else it doesn't activate in our situations.

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