[MacPorts] #65060: blender: Undefined boost symbols

MacPorts noreply at macports.org
Sat Apr 23 21:59:33 UTC 2022


#65060: blender: Undefined boost symbols
----------------------+------------------------
  Reporter:  srasku   |      Owner:  jasonliu--
      Type:  defect   |     Status:  assigned
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:  2.7.2
Resolution:           |   Keywords:
      Port:  blender  |
----------------------+------------------------

Comment (by jasonliu--):

 Replying to [comment:1 ryandesign]:
 > Replying to [ticket:65060 srasku]:
 > > {{{
 > > :info:build ld: warning: dylib (...) was built for newer macOS version
 (11.2) than being linked (11.0)
 > > }}}
 >
 > This is probably not a problem. If it is, it can be solved by increasing
 the revision of the ports that provide those libraries to rebuild them, or
 updating them to a newer version if one is available. It occurred because
 those libraries were built on macOS 11.2 by MacPorts 2.6.4 which did not
 fully support macOS versions greater than 11.0.x. That problem was fixed
 in MacPorts 2.7.0.
 >
 > > {{{
 > > :info:build Undefined symbols for architecture x86_64:
 > > :info:build   "boost::locale::base_message_format<char>::id",
 referenced from:
 > > :info:build       _bl_locale_set in
 libbf_intern_locale.a(boost_locale_wrapper.cpp.o)
 > > }}}
 >
 > These are certainly problems. I don't see any `-lboost...` or
 `/opt/local/lib/libboost....dylib` in the log so maybe that just needs to
 be added in the right places. Surely this port must've worked before and
 I'm not sure what broke since then, but my hunch would be the
 [changeset:d04cb1adc1179bc8a7b0dc04b18b002fbd4fddb3/macports-ports
 migration to the boost portgroup] and multiple separate boost ports. Maybe
 this port needs additional changes for that to work properly.

 If you follow the "referenced from" messages all the way down the chain
 until the end, the undefined symbols error appears to be related to
 {{{usd_writer_hair.cc}}}, {{{usd_hierarchy_iterator.cc}}}, etc., which
 {{{#include}}} portions of the USD library, which is one of Blender's
 dependencies. The USD port was also migrated to the boost portgroup at the
 same time as Blender, and as far as I can tell, the USD port is still
 functioning fine? I'll do some testing to see whether I can reproduce and
 troubleshoot the error on my local machine.

 If the other warnings can be resolved by a simple revbump, I'll take care
 of those after working on the undefined symbols error, since that one
 prevents building.

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


More information about the macports-tickets mailing list