[MacPorts] #63410: pango @1.42.4: Undefined symbols _CFArrayGetValueAtIndex _CFLocaleCopyPreferredLanguages _CFRelease _CFStringGetCString (was: Failed to build pango: command execution failed)

[MacPorts]

#63410: pango @1.42.4: Undefined symbols _CFArrayGetValueAtIndex
_CFLocaleCopyPreferredLanguages _CFRelease _CFStringGetCString
-------------------------+------------------------
  Reporter:  randys8362  |      Owner:  ryandesign
      Type:  defect      |     Status:  assigned
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.7.1
Resolution:              |   Keywords:
      Port:  pango       |
-------------------------+------------------------
Changes (by ryandesign):

 * status:  new => assigned
 * owner:  (none) => ryandesign
 * port:  x11/pango => pango


Comment:

 The log says:

 {{{
 :info:build Undefined symbols for architecture x86_64:
 :info:build   "_CFArrayGetValueAtIndex", referenced from:
 :info:build       _pango_language_get_default in pango-language.o
 :info:build   "_CFLocaleCopyPreferredLanguages", referenced from:
 :info:build       _pango_language_get_default in pango-language.o
 :info:build   "_CFRelease", referenced from:
 :info:build       _pango_language_get_default in pango-language.o
 :info:build   "_CFStringGetCString", referenced from:
 :info:build       _pango_language_get_default in pango-language.o
 :info:build ld: symbol(s) not found for architecture x86_64
 }}}

 I don't recognize this failure. It built fine for us back when pango was
 updated to this version a long time ago, but it's possible that recent
 updates in one of pango's dependencies might have caused this new problem.
 Most other users get binaries from our server and would not notice a build
 failure; you use a nonstandard prefix so you build everything from source
 and would be among the first to discover such breakage.

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