[MacPorts] #69698: boost @1.76: error: no member named 'result_of' in namespace 'boost'

MacPorts noreply at macports.org
Tue May 28 10:42:55 UTC 2024


#69698: boost @1.76: error: no member named 'result_of' in namespace 'boost'
----------------------+-----------------------
  Reporter:  Gandoon  |      Owner:  michaelld
      Type:  defect   |     Status:  assigned
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:  2.9.3
Resolution:           |   Keywords:
      Port:  boost    |
----------------------+-----------------------

Comment (by Gandoon):

 Two quick notes:

 As there recently was made available an updated `qBittorrent
 @4.6.5_0+gui`, I tried again and I got the same error as before with the
 unversioned `boost` active. A deactivation of this let `qBittorrent` build
 without problems.

 In addition, it seems as if my `vtk @9.3.0_0+ffmpeg+python311+qt5+xdmf`
 does not really care if the unversioned `boost` is active or not, at least
 not during a `rev-upgrade` despite that it lists `port:boost` as a
 dependency. Thus I assume that any linking is working as it should,
 presumably against my installed `boost176
 @1.76.0_10+clang14+cmake_scripts+no_single+no_static+python312`. I assume
 that the next time `vtk` is updated (which seems due), especially if the
 library dependency on `port:boost` is still there, I will see what
 happens. I expect a complaint about dependencies not being met during
 build, but as the library ''is'' there and seemingly linked to, not having
 `boost` there won't have any implications in real life. As far as I can
 see, the port just soft-links select `/opt/local/lib/libboost*` instances
 to the `boost176` installation anyway. I am guessing that it may be the
 presence of libraries and includes in `/opt/local/lib` and
 `/opt/local/include/boost/` in the top-level directories that throws
 `qBittorrent` builds off. It expects `boost181` but looks in the mentioned
 locations, finding `boost176` content instead of
 `/opt/local/libexec/boost/1.81/`. Anyway, this issue seem to be a minor
 inconvenience more than anything.

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


More information about the macports-tickets mailing list