boost: Update to 1.65.1

[eborisch (Eric A. Borisch)]

Portfile patch attached. Some of the patchfiles can go away, too.

[ryandesign (Ryan Carsten Schmidt)]

Duplicate of #50572.

[michaelld (Michael Dickens)]

I just attached a full diff for the Portfile and patch files between 1.59.0 and proposed 1.60.0.

All of my dependent ports will have to be rebuilt because the Boost ABI has been changed enough to be incompatible.

Other please review and test.

[mamoll (Mark Moll)]

Ports that depend on Boost.Python may not compile. I tried ompl (a port I maintain) with Boost 1.60 and it definitely doesn't compile. See, e.g., ​https://bitbucket.org/ompl/ompl/issues/210/compilation-failure-with-boost-1600 and ​https://github.com/hhatto/pgmagick/issues/4

[mouse07410 (Mouse)]

This should be reported to the Boost bug tracker, IMHO.

[michaelld (Michael Dickens)]

Initial testing the GNU Radio ports shows compatibility with a rev-bump. I didn't test them all, but the all of the primary related ports and some of the dependent ports build just fine using Boost 1.60.0 out of the box. They all require a rev-bump rebuild due to updated boost ABI.

[g.korovkin@…]

Cc Me!

[wuyongwei@…]

I can confirm that it basically works, but I have to rebuild mkvtoolnix to make it work again, probably due to a regex ABI change. Is there a away to trigger the rebuild of other ports?

[ryandesign (Ryan Carsten Schmidt)]

A developer must manually identify all ports that use boost, manually increase their revisions, verify they all build and if necessary fix any bugs, and commit everything together. This involved process is why I haven't done it.

[wuyongwei@…]

Cc Me!

[wuyongwei@…]

The patch is updated (against ports SVN). It seems to work well for me, though I have to rebuild mkvtoolnix again, which is a pain. However, I am happy I have finally a working Boost 1.61.0 port on my local drive now. ;-)

[michaelld (Michael Dickens)]

Thanks for posting the patch.

Ditto what Ryan wrote about not updating. Boost is used by a ton of ports. Finding and rev-bumping all of those will take a LOT of time. I just don't have that sort of time right now. I have a conference coming up in mid-September at which I should have time. So, if nobody has been able to address this ticket by then, I'll give it a go.

[wuyongwei@…]

If the ABI change happens frequently and we do not have a versioning mechanism for the boost dylibs, does it make sense that we make all the dependent ports link with the static libs? It will be a big change, but will likely reduce future breakages.

[ryandesign (Ryan Carsten Schmidt)]

ABI changes happen with most new versions of boost. It's not really our responsibility to develop a versioning mechanism; it's up to the developers of boost to do that, and they do not appear to have any interest in doing so.

We do not want to link with static libraries, unless a particular build system makes it impossible to do otherwise.

Using static libraries would not solve the problem, it would just hide the problem until later. We don't want to do that either.

[wuyongwei@…]

Replying to ryandesign@…:

Using static libraries would not solve the problem, it would just hide the problem until later. We don't want to do that either.

There are two problems with new boost versions:

1. A port may fail to compile with the new boost.
2. A port may compile fine, but the binary compiled with the old boost version does not work with the new dylib.

Static linking does not solve the first problem, but it will solve the second. Probably we still need to test other ports when there is a new boost version, but I do not think we need to bump the version of all other dependent ports and make new releases then.

[larryv (Lawrence Velázquez)]

No, using static libraries without immediate revbumping is not an option. The builds of such dependents would not be reproducible. A foo @1.2_3 built before a boost upgrade would not be the same as a foo @1.2_3 built immediately after, but we would not be able to distinguish them without technically invasive measures.

[ATL-Flaneur (Andreas Yankopolus)]

Cc Me!

[maehne (Torsten Maehne)]

Cc Me!

[michaelld (Michael Dickens)]

clearly I didn't have time at the conference. no idea when I will have time. boost has been updated to 1.62.

[michaelld (Michael Dickens)]

I just pushed the branch ​https://github.com/macports/macports-ports/tree/boost_update where work on this ticket can happen. I've updated both boost and the ports that I have installed that depend on boost ("port dependents boost"). I'm quite sure there are more ports that depend on boost than those I updated. I have had no issues thus far with the update; everything including boost build cleanly (or, at least as cleanly as the prior boost provided). Let's get updates to this branch in place, verified and tested, then we can merge the whole shebang at once into the master -- and, keep this branch around for future boost updates, since knowing which ports to rev-bump is part of the issue.

[larryv (Lawrence Velázquez)]

Replying to michaelld:

and, keep this branch around for future boost updates, since knowing which ports to rev-bump is part of the issue.

There’s nothing wrong with using a topic branch for this, but I would rather you rebase it onto master when you’re done, delete it, and recreate it when the next boost update happens. We want the keep the master history as linear as possible (which means no merge commits) and don’t want to encourage long-lived branches like we had in the old repository.

[michaelld (Michael Dickens)]

Agreed. I'll keep a branch in my personal fork that holds the info we need to do updates, to make future boost updates faster & easier.

[akimd (Akim Demaille)]

So what should end users, like me, do to get a recent Boost?

[michaelld (Michael Dickens)]

Boost 1.63.0 has been released. I'll be updating this branch & testing with my boost ports shortly. I'll also attach a patch to this ticket for folks interested in trying out this new boost version.

[michaelld (Michael Dickens)]

Update is in place in the same branch (​https://github.com/macports/macports-ports/tree/boost_update), which is refreshed to the current MP GIT master.

I'll attach a patch as well, which folks can test using something like (assuming "~/Downloads/boost_update_to_1.63.0.diff" is where the patch is downloaded to):

cd $(port dir boost)
sudo chmod -R a+rw .
patch -p1 < ~/Downloads/boost_update_to_1.63.0.diff
sudo port selfupdate

and, then the new boost should be built and installed.

For my Boost using ports, this update works after rebuilding them; these libraries are not drop-in ABI replacements for either 1.59.0 or 1.62.0.

Please submit feedback on this ticket.

[michaelld (Michael Dickens)]

Here's the command I use (approximately) to update boost dependent ports:

sudo -s
for tf in ${port dependents boost | awk '{ print $1 }'}; do \
port -n upgrade --force ${tf} \
done

[akimd (Akim Demaille)]

Thanks for this. But I'm quite puzzled by the number of local patches that you still have to apply. Upstream does not want to apply them all? I can see that some have been, or became useless, but not all.

[michaelld (Michael Dickens)]

I know little about why Boost patches are in place. I can see from the Portfile comments that at last some portion of the patches were integrated into Boost a while back, but clearly not all of them. In my belief, if the patches can still be applied then they should continue to be used, that there's a reason they are there in the first place & are highly likely to continue to be needed.

That said, if folks want to do testing by commenting out any specific patch then I'd welcome feedback as to if/how that worked. I don't have time to do this just right now.

[michaelld (Michael Dickens)]

Boost 1.64.0 is out. In my initial testing, the only required changes from 1.63.0 are the version & checksums; there are a few patch tweaks to get them clean, but they do work.

[michaelld (Michael Dickens)]

Minor / easy fix required to <boost/serialization/array.hpp>: add in

#include <boost/serialization/array_wrapper.hpp>

after

#include <array>

After that, my ports that use Boost are building thus far (at least with respect to boost issues). source-highlight and assimp built without this change.

[michaelld (Michael Dickens)]

Has duplicate #54105 .

[gaming-hacker (G Alexander)]

why doesn't macports create it's own github fork of boost? create subtrees, apply patches, clean it up, etc. create a custom build bot and let the bot thrash the updates for regression testing.

[ryandesign (Ryan Carsten Schmidt)]

Replying to gaming-hacker:

why doesn't macports create it's own github fork of boost? create subtrees, apply patches, clean it up, etc. create a custom build bot and let the bot thrash the updates for regression testing.

Why would we want to do that, as opposed to the method we've always used for incorporating patches into ports?

If a MacPorts contributor, or anyone, wants to help develop boost, they can certainly do so in whatever way they want, including forking a repository and sending pull requests, if that's a contribution method the developers of boost support. But that needn't have anything to do with how the MacPorts boost portfile operates.

[l2dy (Zero King)]

Replying to michaelld:

Can you share a patch or update the boost_update branch?

[michaelld (Michael Dickens)]

Yeah; sure. Thee's so much work to do to update boost that we rarely get around to doing it!

I've attached a tarball of the port directory, with updates to patches so that they are clean (note that "files/patch-log-setup-link.diff" has been removed). I've included the patch that fixes boost::serialization::make_array to be included as part of boost::serialization, as it was in 1.63 and will be in 1.65; not sure if we should actually include it or not.

[gaming-hacker (G Alexander)]

to get the mpi lib to compile for OSX i had to add this patch

​https://github.com/boostorg/mpi/commit/f5bdcc1ebfe954bb64835f2a0efd94471da42207

and voila, i have a complete library build 1.64 for osx 10.12.6 with most libs with mpi no python.

[michaelld (Michael Dickens)]

@gaming-hacker: what's a 'port' commandline that shows the error that requires this patch to fix?

[gaming-hacker (G Alexander)]

when building with mpi libs, the build crashes because this header file is not included/doesn't exist in new boost versions.

"#include <boost/serialization/detail/get_data.hpp>"

[michaelld (Michael Dickens)]

1.65.0 is out. should fix the major issues in 1.64.0. Hopefully doesn't introduce more.

​http://www.boost.org/users/history/version_1_65_0.html

[michaelld (Michael Dickens)]

I just attached a tarball of my 1.65.0 boost port. The primary change is removing the now-integrated patch for boost/serialization/array.hpp to add the array wrapper. Otherwise, it's just business as usual.

I'll attach the build log too (macOS 10.12.6 latest, Xcode latest, just default variants), and note a warning about building and/or using the deprecated coroutine module, which has been replaced with coroutine2. I didn't look into fixing this issue (yet).

This version of boost seems to work for my projects (GNU Radio / Volk / UHD / GR OOT modules). It also built cleanly the other ports that depend on it that I have installed (assimp and source-highlight).

Please test this version & report back here ports that work for you (e.g., with a rev-bump) -- and let's find a way to get it merged into the ports!

[michaelld (Michael Dickens)]

boost 1.65.0 build log for macOS 10.12.6 latest, Xcode latest, default variants

[mamoll (Mark Moll)]

boost 1.65.0 build log for macOS 10.12.6 latest, Xcode latest, +openmpi +python36 variants

[mamoll (Mark Moll)]

I had to update the patch file patch-libs-mpi-build-Jamfile.v2.diff to get boost 1.65 to compile with the +openmpi and +python36 variants enabled. I have attached the build log and updated port file directory. I'm still testing other boost-depedendent ports, but I have already discovered one problem for cmake-based ports. This no longer works:

find_package(Boost COMPONENTS python)

because there is no more libboost_python-mt.dylib. There is only libboost_python3-mt.dylib. With the old port, both libraries existed.

[michaelld (Michael Dickens)]

@mamoll: Thanks!

Yes, looks like if you do +python27 (the default), then you get libboost_python-mt.dylib. I assume if +python36 then in CMake you have to do find_package(Boost COMPONENTS python3) ... a small but critical change to be noted.

[mamoll (Mark Moll)]

As a workaround, this seems to also do the trick:

sudo ln -s /opt/local/lib/libboost_python3-mt.dylib /opt/local/lib/libboost_python-mt.dylib

[michaelld (Michael Dickens)]

I've attached my boost directory with the updates from Mark for Python3 and MPI as well as 1.65.1. All patches apply cleanly for the various variants. All of my boost-dependent ports require rebuilding to run, as is usual with updated boost (sigh).

I'm not including a post-destroot for linking python3-mt to python-mt, since that seems "dangerous" & really for developers only & better fixed in CMake or elsewhere. Most developers I know have moved to "python2" and "python3", with "python" being understood to being "python2" ... so "python3" is really it's own separate concept, in my experience.

[mamoll (Mark Moll)]

Replying to michaelld:

I'm not including a post-destroot for linking python3-mt to python-mt, since that seems "dangerous" & really for developers only & better fixed in CMake or elsewhere. Most developers I know have moved to "python2" and "python3", with "python" being understood to being "python2" ... so "python3" is really it's own separate concept, in my experience.

Boost can only be installed with only python variant. Many packages that look for libboost-python need to be updated. It'd be a big help if the FindBoost.cmake module could be patched to correctly find boost.python3 when used like so:

find_package(Boost COMPONENTS python)

[gaming-hacker (G Alexander)]

Replying to michaelld:

Nice work removing all the dead wood. It seems there are a lot of other ports that still use older versions of libs. I tried to force build boost and all dependencies with clang5, no gnu-gcc*, no apple compiler and failed. I did manage to chop and hack the portfile and variants.conf to finally obtained a complete boost lib and dependents build with only clang4 but without any python.

[ryandesign (Ryan Carsten Schmidt)]

Replying to michaelld:

I've attached my boost directory with the updates from Mark for Python3 and MPI as well as 1.65.1. All patches apply cleanly for the various variants. All of my boost-dependent ports require rebuilding to run, as is usual with updated boost (sigh).

So can I commit this (along with revbumping all ports linking with boost, of course) or is something else still needed?

[michaelld (Michael Dickens)]

I'm good with committing & rev-bumping. LOTS of ports to rev-bump, which is why I never get to it ;)

Shortly I'll be committing updates to cmake that work with this release.

[ryandesign (Ryan Carsten Schmidt)]

Do you mean that your forthcoming cmake update should be committed first, or this boost update?

[ryandesign (Ryan Carsten Schmidt)]

I also notice you added -d2 to build.args a second time. I assume that's not needed?

[michaelld (Michael Dickens)]

Yes remove the redundant -d2. No need for it. My bad.

The updates to cmake are committed, so cmake and cmake devel seem to be working now with Xcode 9 & should recognize and correctly find (without warnings) Boost 1.65.1 (and earlier).

If you have the time to deal with rev-bumps, then please make it so whenever you can!

[fredowski]

Hi, is there a github fork/branch where I could see the current work on the boost update? Michael mentioned the boost_update branch in some previous comment but I think that is now in some fork of macports? Is it correct that all the following ports need revision updates, when the version of boost is changed?

FriedrichsMacBook:macports-ports fritz$ find . -name Portfile -exec grep -l boost {} \;
./aqua/luminance-hdr/Portfile
./aqua/LyX/Portfile
./aqua/qtiplot/Portfile
./archivers/innoextract/Portfile
./audio/mpd/Portfile
./audio/ncmpcpp/Portfile
./audio/xmms2/Portfile
./cad/freecad/Portfile
./cad/LibreCAD/Portfile
./databases/mongodb/Portfile
./databases/mysql55-connector-cpp/Portfile
./databases/mysql57/Portfile
./databases/rethinkdb/Portfile
./databases/simplevoc-open/Portfile
./databases/soci/Portfile
./devel/akonadi/Portfile
./devel/arabica/Portfile
./devel/aspcud/Portfile
./devel/boost/Portfile
./devel/boost-build/Portfile
./devel/boost-gil-numeric/Portfile
./devel/boost-jam/Portfile
./devel/boost-process/Portfile
./devel/codeblocks/Portfile
./devel/fbthrift/Portfile
./devel/flusspferd/Portfile
./devel/folly/Portfile
./devel/gecode/Portfile
./devel/gource/Portfile
./devel/icu/Portfile
./devel/json_spirit/Portfile
./devel/kick/Portfile
./devel/libbert/Portfile
./devel/libftdi/Portfile
./devel/liblightgrep/Portfile
./devel/libnifalcon/Portfile
./devel/libphonenumber-cpp/Portfile
./devel/libpst/Portfile
./devel/librets/Portfile
./devel/LucenePlusPlus/Portfile
./devel/mongo-cxx-driver/Portfile
./devel/monotone/Portfile
./devel/mstch/Portfile
./devel/orocos-kdl/Portfile
./devel/orocos-rtt/Portfile
./devel/poedit/Portfile
./devel/srecord/Portfile
./devel/strigi/Portfile
./devel/tao/Portfile
./devel/thrift/Portfile
./devel/thrift-devel/Portfile
./devel/valgrind/Portfile
./devel/vcsn/Portfile
./devel/wangle/Portfile
./devel/xmlwrapp/Portfile
./devel/yaml-cpp/Portfile
./editors/sigil/Portfile
./editors/textmate2/Portfile
./finance/bitcoin/Portfile
./finance/ledger/Portfile
./finance/litecoin/Portfile
./finance/QuantLib/Portfile
./fuse/encfs/Portfile
./games/bastet/Portfile
./games/fife/Portfile
./games/glob2/Portfile
./games/pingus/Portfile
./games/PlasmaClient/Portfile
./games/wesnoth/Portfile
./games/widelands/Portfile
./gis/cgal/Portfile
./gis/libkml/Portfile
./gis/liblas/Portfile
./gis/libpcl/Portfile
./gis/mapnik/Portfile
./gis/orfeotoolbox/Portfile
./gis/rsgislib/Portfile
./gnome/glom/Portfile
./graphics/agave/Portfile
./graphics/assimp/Portfile
./graphics/assimp2/Portfile
./graphics/enblend/Portfile
./graphics/exempi/Portfile
./graphics/field3d/Portfile
./graphics/gpick/Portfile
./graphics/hugin-app/Portfile
./graphics/inkscape/Portfile
./graphics/inkscape-devel/Portfile
./graphics/lib2geom/Portfile
./graphics/libcdr/Portfile
./graphics/libcdr-0.1/Portfile
./graphics/libfreehand/Portfile
./graphics/libmspub/Portfile
./graphics/libopenraw/Portfile
./graphics/libpagemaker/Portfile
./graphics/libvisio/Portfile
./graphics/libvisio-0.1/Portfile
./graphics/mkhexgrid/Portfile
./graphics/ogre/Portfile
./graphics/openexr/Portfile
./graphics/OpenSceneGraph/Portfile
./graphics/OpenSceneGraph-devel/Portfile
./graphics/openvrml/Portfile
./graphics/povray/Portfile
./graphics/scantailor/Portfile
./graphics/synfig/Portfile
./graphics/vigra/Portfile
./kde/digikam/Portfile
./kde/kde4-workspace/Portfile
./kde/kdenetwork-strigi-analyzers/Portfile
./kde/kdepim4/Portfile
./kde/kdepim4-runtime/Portfile
./kde/kdepimlibs4/Portfile
./kde/kdevplatform/Portfile
./kde/kget/Portfile
./kde/kgraphviewer/Portfile
./kde/kig/Portfile
./kde/ktorrent4/Portfile
./kde/libktorrent/Portfile
./kde/py-pykde4/Portfile
./kde/rocs/Portfile
./kde/umbrello/Portfile
./lang/opensaml/Portfile
./lang/sdcc/Portfile
./math/caffe/Portfile
./math/cvc4/Portfile
./math/dolfin/Portfile
./math/fityk/Portfile
./math/mlpack/Portfile
./math/stp/Portfile
./math/viennacl/Portfile
./math/vowpal_wabbit/Portfile
./math/xylib/Portfile
./multimedia/mkvtoolnix/Portfile
./multimedia/shenidam/Portfile
./net/deluge/Portfile
./net/libtorrent-rasterbar/Portfile
./net/metaproxy/Portfile
./net/pdns-recursor/Portfile
./net/tcpflow/Portfile
./net/yazproxy/Portfile
./perl/p5-type-tiny-xs/Portfile
./php/php-xslcache/Portfile
./print/scribus/Portfile
./python/py-bob/Portfile
./python/py-bob-ap/Portfile
./python/py-bob-blitz/Portfile
./python/py-bob-core/Portfile
./python/py-bob-db-atnt/Portfile
./python/py-bob-db-base/Portfile
./python/py-bob-db-iris/Portfile
./python/py-bob-db-mnist/Portfile
./python/py-bob-db-verification-utils/Portfile
./python/py-bob-db-wine/Portfile
./python/py-bob-extension/Portfile
./python/py-bob-io-audio/Portfile
./python/py-bob-io-base/Portfile
./python/py-bob-io-image/Portfile
./python/py-bob-io-matlab/Portfile
./python/py-bob-io-video/Portfile
./python/py-bob-ip-base/Portfile
./python/py-bob-ip-color/Portfile
./python/py-bob-ip-draw/Portfile
./python/py-bob-ip-facedetect/Portfile
./python/py-bob-ip-gabor/Portfile
./python/py-bob-ip-optflow-hornschunck/Portfile
./python/py-bob-ip-optflow-liu/Portfile
./python/py-bob-learn-activation/Portfile
./python/py-bob-learn-boosting/Portfile
./python/py-bob-learn-em/Portfile
./python/py-bob-learn-libsvm/Portfile
./python/py-bob-learn-linear/Portfile
./python/py-bob-learn-mlp/Portfile
./python/py-bob-math/Portfile
./python/py-bob-measure/Portfile
./python/py-bob-sp/Portfile
./python/py-bottleneck/Portfile
./python/py-exiv2/Portfile
./python/py-ffc/Portfile
./python/py-graph-tool/Portfile
./python/py-pynds/Portfile
./python/py-simplejson/Portfile
./python/py-stfio/Portfile
./science/alps/Portfile
./science/ALPSCore/Portfile
./science/ALPSMaxent/Portfile
./science/bali-phy/Portfile
./science/chemkit/Portfile
./science/ckon/Portfile
./science/collada-dom/Portfile
./science/cufflinks/Portfile
./science/eo/Portfile
./science/fcl/Portfile
./science/gerbil/Portfile
./science/gnss-sdr/Portfile
./science/gnuradio/Portfile
./science/gr-air-modes/Portfile
./science/gr-ais/Portfile
./science/gr-baz/Portfile
./science/gr-dvbs/Portfile
./science/gr-dvbs2/Portfile
./science/gr-dvbt/Portfile
./science/gr-fcdproplus/Portfile
./science/gr-foo/Portfile
./science/gr-fosphor/Portfile
./science/gr-ieee802-11/Portfile
./science/gr-ieee802-15-4/Portfile
./science/gr-iqbalance/Portfile
./science/gr-lora/Portfile
./science/gr-lte/Portfile
./science/gr-mac/Portfile
./science/gr-ofdm/Portfile
./science/gr-osmosdr/Portfile
./science/gr-pcap/Portfile
./science/gr-pyqt/Portfile
./science/gr-rds/Portfile
./science/gr-specest/Portfile
./science/gromacs/Portfile
./science/Gyoto/Portfile
./science/htcondor/Portfile
./science/iAIDA/Portfile
./science/magicspp/Portfile
./science/metview/Portfile
./science/ompl/Portfile
./science/openscad/Portfile
./science/peekabot-client/Portfile
./science/peekabot-server/Portfile
./science/playerstage-player/Portfile
./science/pythia/Portfile
./science/scidavis/Portfile
./science/seqan-apps/Portfile
./science/spot/Portfile
./science/stimfit/Portfile
./science/uhd/Portfile
./science/volk/Portfile
./science/volk-gnss-sdr/Portfile
./security/bulk_extractor/Portfile
./security/shibboleth/Portfile
./security/xmltooling/Portfile
./sysutils/cputhrottle/Portfile
./sysutils/fasd/Portfile
./sysutils/gearmand/Portfile
./textproc/cicada/Portfile
./textproc/expgram/Portfile
./textproc/freeling/Portfile
./textproc/highlight/Portfile
./textproc/lader/Portfile
./textproc/libetonyek/Portfile
./textproc/libodfgen/Portfile
./textproc/librevenge/Portfile
./textproc/mgizapp/Portfile
./textproc/mosesdecoder/Portfile
./textproc/source-highlight/Portfile
./textproc/zorba/Portfile
./textproc/zunda/Portfile
./www/logstalgia/Portfile
FriedrichsMacBook:macports-ports fritz$ 

[michaelld (Michael Dickens)]

There is no branch that's valid any longer. Just the tarballs on this ticket. Anyone have time to go through the list here & rev-bump them all for the updated boost?

[ryandesign (Ryan Carsten Schmidt)]

I still plan to do it.

[gaming-hacker (G Alexander)]

It seems easier until boost 1.59 gets deprecated or dealt with, I created local port directory, download the 1.65.1 files, extract, run portindex and port install boost. This finds the latest boost without changing all of the libs.

--->  Computing dependencies for boost
--->  Fetching distfiles for boost
--->  Verifying checksums for boost
--->  Extracting boost
--->  Applying patches to boost
--->  Configuring boost
--->  Building boost
--->  Staging boost into destroot
--->  Installing boost @1.65.1_0+clang50+no_single+no_static+openmpi_devel+python27
--->  Activating boost @1.65.1_0+clang50+no_single+no_static+openmpi_devel+python27
--->  Cleaning boost
--->  Updating database of binaries
--->  Scanning binaries for linking errors               
--->  No broken files found.

I installed highlight

--->  Computing dependencies for highlight
--->  Fetching archive for highlight
--->  Attempting to fetch highlight-3.40_0.darwin_16.x86_64.tbz2 from https://packages.macports.org/highlight
--->  Attempting to fetch highlight-3.40_0.darwin_16.x86_64.tbz2 from http://sea.us.packages.macports.org/macports/packages/highlight
--->  Attempting to fetch highlight-3.40_0.darwin_16.x86_64.tbz2 from http://ywg.ca.packages.macports.org/mirror/macports/packages/highlight
--->  Fetching distfiles for highlight
--->  Attempting to fetch highlight-3.40.tar.bz2 from https://distfiles.macports.org/highlight
--->  Verifying checksums for highlight                                              
--->  Extracting highlight
--->  Applying patches to highlight
--->  Configuring highlight
--->  Building highlight
--->  Staging highlight into destroot
--->  Installing highlight @3.40_0
--->  Activating highlight @3.40_0
--->  Cleaning highlight
--->  Updating database of binaries
--->  Scanning binaries for linking errors
--->  No broken files found.

[mamoll (Mark Moll)]

Is there a timeline on when this gets merged? There is at least one other issue that would go away with boost 1.65: #55228. I am wondering if I should bother to get a patch to fix this for the current version of boost.

[ryandesign (Ryan Carsten Schmidt)]

It's not as simple as "merging" the update to boost 1.65.1. All ports depending on boost should also be revbumped. I am currently working on making the buildbot faster. After that, I will do the boost update and revbumps. I don't have a specific timeline for you.

[ryandesign (Ryan Carsten Schmidt)]

In 416525222a7c68e719d9c836c54cff1a6a352e73/macports-ports:

boost: Update to 1.65.1

Closes: #50671

[ryandesign (Ryan Carsten Schmidt)]

In f3dd036d4a4e2b8fc245d4fce27b6c96e298af5f/macports-ports:

Rebuild ports with boost 1.65.1

See: #50671

[akimd (Akim Demaille)]

Great job!