[MacPorts] #71503: libfmt11 cannot be linked to on Tiger PPC

[MacPorts]

#71503: libfmt11 cannot be linked to on Tiger PPC
-----------------------+-----------------------
  Reporter:  glebm     |      Owner:  mascguy
      Type:  defect    |     Status:  assigned
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:
Resolution:            |   Keywords:  tiger ppc
      Port:  libfmt11  |
-----------------------+-----------------------

Comment (by kencu):

 libfmt11's cmake and pkgconfig files are here:

 {{{
 /opt/local/lib/libfmt11/cmake/fmt/fmt-config.cmake
 /opt/local/lib/libfmt11/cmake/fmt/fmt-config-version.cmake
 /opt/local/lib/libfmt11/cmake/fmt/fmt-targets-relwithdebinfo.cmake
 /opt/local/lib/libfmt11/cmake/fmt/fmt-targets.cmake
 /opt/local/lib/libfmt11/pkgconfig/fmt.pc
 }}}

 they are not in the usual place for these kinds of files, probably because
 there are a number of libfmt versions available:

 {{{
 % port search libfmt
 libfmt4 @4.1.0 (devel)
     an open-source formatting library

 libfmt8 @8.1.1_2 (devel)
     An open-source formatting library

 libfmt9 @9.1.0 (devel)
     An open-source formatting library

 libfmt10 @10.2.1 (devel)
     An open-source formatting library

 libfmt11 @11.0.2 (devel)
     An open-source formatting library

 }}}

 and they would all trample each other if they were all installed into the
 default prefix.

 Usually what we try to do is have the desired one (usually the latest one)
 found by default and the others require forcing of variables to be found,
 but that doesn't always work out right and so sometimes they are all
 installed into various subdirs and you need to spec them with a pkgconfig
 PATH addition or cmake module path addition to spec the one you want used.

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