• https://boostorg.jfrog.io/artifactory/main/release/1.77.0/source/ (Download)

• (2022-01-06) Updated to version: boost-1.77.0
• (2021-11-22) Updated to version: boost-1.76.0
• (2021-09-19) Updated to version: boost_1_76_0
• (2021-09-04) Updated to version: boost_1_77_0
• (2021-06-22) Updated to version: boost_1_76_0
• (2021-04-28) Updated to version: boost_1_73_0
• (2021-02-01) Updated to version: boost_1_72_0
• (2020-11-05) Updated to version: boost_1_70_0
• (2020-08-16) Updated to version: boost_1_67_0
• (2018-12-14) Updated to version: boost_1_66_0

Log message:
zap a few PKGNAME-sub which are now default
(and also duplicated EPOCH-sub which make little sense in db/{v3,v4}

Log message:
Build -md on riscv64, now with the required bits present in libcontext
Build-tested with icinga/core2 and net/powerdns_recursor, runtime tested
with a few test programs.  ok Brad (maintainer)

Log message:
Disable boost-md on riscv64
The make_fcontext/jump_fcontext etc bits aren't implemented in
libboost_context-mt.so, leading to link-type failures in consumer ports.

Log message:
adjust ports with hardcoded Python 3.8 versions, ok kmos@

Log message:
fix boost @conflict line
-@conflict boost-md-<1.76.0v0
+@conflict boost-md-<1.76.0p0v0

Log message:
simply arch list for -md by moving to NOT_FOR_ARCHS, from brad

Log message:
move Boost::stacktrace libraries from md to the main package, from Brad.
"Builds on all of the Clang archs and sparc64. It was disabled initially for
a build issue on arm, but that was before switching to Clang.
NetBSD disables context, coroutine and fiber on a few archs like we do, but
not stacktrace and as far as I can see it does not have any MD dependencies."

Log message:
Rollback to boost 1.67.0
There were some errors reported with it. Especially with
net/libtorrent-rasterbar. This meant that net/qbittorrent and net/deluge no
longer wokred. tb@ und mariani@ have found out that it is definitely the boost
update to 1.77. Brad has found out tha the problem can be solved by building
libtorrent-rasterbar with -O0.
Unless we understand the mechanism for the failure and are sure it's a
libtorrent-rasterbar problem rather than a boost one, sthen@ suggested to back
it out.
OK mariani@, sthen@ and Brad

Log message:
update to Boost 1.77, from Brad, rsadowski helped fixing the few ports
that had problems in bulk

Log message:
boost: A little bit of Makefile cleaning up and integrate the LibreSSL
fix as was commited upstream.
From Brad.

Log message:
Add missing patch to unbreak the build on sparc, hint by Brad

Log message:
Update Boost to 1.76
https://www.boost.org/users/history/version_1_74_0.html
https://www.boost.org/users/history/version_1_75_0.html
https://www.boost.org/users/history/version_1_76_0.html
Update diff from Brad. Arm64 bulk build by phessler, amd64 bulk build by me.
Feedback from many. OK tb@

Log message:
devel/boost: fix upcoming build failure in dependent ports
Use accessors instead of reaching into SSL_CTX. The requisite
accessors have been available since LibreSSL 2.7.2 and are thus
present in all supported versions.
positive feedback from brad, looks good to jsing

Log message:
Update MASTER_SITES url
https://www.boost.org/users/news/boost_has_moved_downloads_to_jfr.html
From Brad, OK sthen@

Log message:
Reorder BOOST_LIBS
"No functional change. Just rearranging the order so they're in alpha order and
having -mt library first."
From Brad (maintainer)

Log message:
Add conflict tag: boost-1.73.0 and leatherman-<1.12.4p0
OK Brad (maintainer), kn@

Log message:
Update Boost to 1.73.0
- https://www.boost.org/users/history/version_1_73_0.html
Update diff from maintainer Brad

Log message:
Reverse the polarity of MODPY_VERSION; default is now 3.x,
if a port needs 2.x then set MODPY_VERSION=${MODPY_DEFAULT_VERSION_2}.
This commit doesn't change any versions currently used; it may be that
some ports have MODPY_DEFAULT_VERSION_2 but don't require it, those
should be cleaned up in the course of updating ports where possible.
Python module ports providing py3-* packages should still use
FLAVOR=python3 so that we don't have a mixture of dependencies some
using ${MODPY_FLAVOR} and others not.

Log message:
Update boost to 1.72.0
Changelogs are here:
https://www.boost.org/users/history/version_1_71_0.html
https://www.boost.org/users/history/version_1_72_0.html
Update diff from Brad Smith (maintainer), OK sthen@

Log message:
Remove some unnecessary patches and fix some typos
Tweak diff from Brad (co-maintainer)

Log message:
Fix build of boost::context on powerpc by removing an unneeded patch.
ok cwen@ brad

Log message:
boost-build has been removed, gc pointless patch
Suggested by Brad (maintainer)

Log message:
Drop boost_python27, boost_numpy27 and boost-build support
Drops one consumer of py2-numpy, upstream numpy is now python3 only.
Dropping all python27 support makes the port simpler and hopefully
future updates easier.  boost-build also leaves as collateral damage,
its python files aren't ready for python3 and it's not clear how useful
they are.
ok Brad, rsadowski@ (maintainers)
ok sthen@ who also helped clear the way

Log message:
Use find -exec {} + to speed up make fake
Down to 4 seconds instead of 4 minutes on my builder.
No bump since there is no change in the resulting package.
ok Brad rsadowski@ (maintainers)

Log message:
update to Boost 1.70, from Brad, bulk tests for various update diffs
(this and earlier releases) me/kmos, various testing/fixes for related
ports from otto daniel bentley rsadowski
ok rsadowski (co-maintainer with Brad)

Log message:
devel/boost: remove patches that are no long necessary now that some
archs have moved to Clang and we no longer mix and match old and new GCC
on non-Clang archs. From Brad, has gone through bulks on sparc64 i386.

Log message:
Unbreak boost 1.67.0 on i386, spotted by sthen@ Thanks
Diff from upstream:
Removed clang-specific branch for x86 DCAS-based loads.
The storage to load from is const-qualified and DCAS via compiler intrinsics
require an unqualified pointer. Use asm implementation instead, which should be
as efficient as intrinsics, if not better, in this case.
https://github.com/boostorg/atomic/commit/6e14ca24dab50ad4c1fa8c27c7dd6f1cb791b534

Log message:
Update boost from 1.66.0 to 1.67.0 (Not to the latest)
This update was requested by aja to update and unbreak productivity/gnucash.
Changlog from upstream:
https://www.boost.org/users/history/version_1_67_0.html

Log message:
Revert previous
While it builds on sparc64 (nowadays), there are still major
runtime issues.
Noted by sthen, otto, Brad

Log message:
Build boost-md on sparc64
OK rsadwoski
"go ahead" plus comment fix from Brad

Log message:
Switch HOMEPAGE to https

Log message:
oops, I missed bumping REVISION-md for the plist change

Log message:
Adding patch I forgot to add when committing update earlier.
Bump REVISION-main again while here.
Pointed out by Nam Nguyen. Thank you.

Log message:
Fix devel/boost python3 bindings
From Nam Nguyen
With input from rsadowski and sthen
Reworked by sthen
Tested by myself and sthen
ok sthen

Log message:
Reverting 1.79 workaround now that ports-gcc has been upgraded
Diff from Brad (maintainer)

Log message:
- Fix userland context switching on powerpc, OpenBSDs ABI differs from the Linux one.
- Fix error in fixed size stack allocator.
Heavy lifting done by George Koehler. ok sthen@ rsadowski@

Log message:
Use ONLY_FOR_ARCHS-md instead of a ".if ${MACHINE_ARCH} ..." tests list
ok sthen@ Brad Smith (maintainer)

Log message:
MAP_STACK is also needed for basic_standard_stack_allocator, found while
testing Icinga 2 development code.  Looks good to otto@, ok Brad

Log message:
replace simple PERMIT_PACKAGE_CDROM=Yes with PERMIT_PACKAGE=Yes

Log message:
Build the MD subpackage on PowerPC.
from Brad and tested by cwen@

Log message:
boost-md needs LIB_DEPENDS/WANTLIB on -main

Log message:
bump all the py3 things, _SYSTEM_VERSION didn't quite work out how
we expected and it's easier|safer to do it this way than fiddle with
pkg_add now. thanks aja for update tests with a quick bulk.

Log message:
build the -md multipackage on aarch64, in pkgsnaps for a while

Log message:
Simplify libc++7 workaround, tweaking config.hpp was enough
Noticed by naddy@, ok Brad (maintainer)

Log message:
Unbreak on clang archs, prefer <string_view> to <experimental/string_view>
ok Brad (maintainer)
libc++7 made <experimental/string_view> a stub containing only
#error "<experimental/string_view> has been removed. Use <string_view> instead."
One can wonder why upstream kept the header at all.

Log message:
enable boost-build
To make your boost.build executables b2 and bjam useful we have to install
some additional files.
Noticed by Ivan Krylov via openbsd@freenode. Thanks!
feedback from semarie@ and aja@, tweaks and ok sthen@

Log message:
Drop bogus -mcpu=v7 on sparc64 (sparc64 == sparc V9)
"looks good" rsadowski@, ok Brad (maintainers)

Log message:
Fix Boost.Locale and unbreak on ports-gcc archs
Since the update to icu4c-63.1, icu4c uses char16_t and others from the
C++11 standard, but eg++-4.9 defaults to -std=gnu++98.
"looks good" rsadowski@, ok Brad (maintainers)

Log message:
Respect PORTPATH and pick up eg++ instead of base g++
"looks good" rsadowski@, ok Brad (maintainers)

Log message:
Print compile commands again (lost in the update to boost-1.65.1)
Without this debugging problems is almost impossible.
"looks good" rsadowski@, ok Brad (maintainers)

Log message:
Add support for boost contexts on i386, arm, amd64, from otto@.
As this brings new libraries on supported architectures, split the
package into -main and -md subpackages, keeping plist updates simpler
and avoiding need for knowledge of supported arches in dependent
ports. Also means that if future ports start picking up the MD
libraries they will be easier to find. (Thanks aja@ for running a
bulk build and check-lib-depends run with an earlier version to
make sure existing ports don't pick up the new libs.)
ok rsadowski@
Bumps for ports using boost as LIB_DEPENDS or RUN_DEPENDS to
follow.

Log message:
set -D_LIBCPP_ENABLE_CXX17_REMOVED_AUTO_PTR in archivers/innoextract
to unbreak with new libc++, newer boost is likely to fix this so add a
comment in devel/boost/Makefile

Log message:
enable Unicode/ICU support in Regex
bulk build on macppc, i386 and amd64 by myself
ok rsadowsk@ (maintainer)

Log message:
Update boost to 1.66.0
Main port changes:
- Add myself as second maintainer
- Licence tag from MIT-like to boost
Changelog:
http://www.boost.org/users/history/version_1_66_0.html
ok jca@ and landry@ (Tested in a bulk, thanks!)
"Fine with me" from Brad (maintainer)

Log message:
Update boost to 1.65.1
Notable port changes.
- Bump all shared libs from 6.0 to 7.0.
- COMPILER= base-clang ports-gcc (Replace ONLY_FOR_ARCHS)
- Remove our user.hpp. Boost detects all compiler features correct.
- Drop all -Wno-* options.
- Drop fiber support. It doesn't build with GCC
- Drop stacktrace support. It doesn't build on arm (spotted by jca@)
- b2 doesn't seem to respect python parameter, we need to run twice with
separate python environments to build both shared libs.
- Zap trailing whitespace
- Add py-numpy as bdep
- Disable precompiled header
- cleanup BJAM_CONFIG
- Drop "-d+2" debug.
Survived a macppc bulk by kirby@
Survived a amd64 bulk by landry@
Build test on sparc64 and arm by jca@ (and many other tests)
Many thanks to all those who made it possible
Final ok landry@, jca@

Log message:
Fix the clang config, really configure for INT128, using clang built-in
defines.
This lets i386 build clang.

Log message:
bump LIBCXX/LIBECXX/COMPILER_LIBCXX ports.

Log message:
use COMPILER_LIBCXX where applicable

Log message:
the tests are wrong, but it's simpler to define the annoying constant to 0

Log message:
clean up Vadim's mess, reorg file so that what we're doing is actually
documented

Log message:
fix nasty clang bug that prevented facter from building

Log message:
Better Clang support for Boost. Allows facter & friends to be built.
To be revisited later if something else will break under CMake.
a lot of valuable input from espie@

Log message:
rename COMPILER as TOOLSET in prevision of impending change

Log message:
improve the clang config: boost hardcodes __attribute__((unused)) on the
wrong compiler, so re-add it (dependent ports will whine a lot less)
tell boost we have threads and int128 (there's not issue about dual
compiler for clang)

Log message:
first try at a clang compile, reuse gcc config so that stuff that builds
does build.
todo:
- enable more stuff
- look closer at the tooling, needs something like the gcc config change
but at least, this allows us to look at the remaining ports.

Log message:
do not redefine unix if it's already there, silences some clang warnings

Log message:
make sure the one test that boost fails on clang conforms to what gcc does

Log message:
Add ${CLANG_ARCHS} to "ONLY_FOR_ARCHS = ${GCC4_ARCHS}" lines to give them
a chance on aarch64.

Log message:
use LIBCXX

Log message:
Honor CXX, CXXFLAGS.
(1) Pass CXX and CXXFLAGS to the configure script run.
(2) Split out the build of the bjam tool from the bootstrap procedure.
(3) Tell the main build to use CXX via user-config.jam.
ok Brad, jca@

Log message:
replace libiconv module

Log message:
boost does not like mixing different compilers at build and compile
time.
We build boost itself with gcc-4.2.1 from base, which doesn't support
the integer scalar type __int128, and this results in a
/usr/local/include/boost/config/user.hpp lacking the "BOOST_HAS_INT128"
define.
When compiling something that depends on boost using a newer compiler
like gcc-4.9 or clang, a code snippet in
/usr/local/include/boost/config/compiler/{clang,gcc}.hpp reactivates
__int128 support, but the code containing typedef declarations
inside /usr/local/include/boost/config/suffix.hpp is never reached,
because /usr/local/include/boost/config/user.hpp lacks "BOOST_HAS_INT128".
Hence, the following errors occur:
/usr/local/include/boost/type_traits/is_integral.hpp:72:1: error: 'int128_type' is not a member of 'boost'
/usr/local/include/boost/type_traits/is_integral.hpp:73:1: error: 'uint128_type' is not a member of 'boost'
As a temporary band-aid, completely disable __int128 support on
OpenBSD.
OK jca@, sthen@

Log message:
Fix Boost.Asio, broken after the removal of SSLv3 support:
/usr/local/include/boost/asio/ssl/impl/context.ipp: In constructor 'boost::asio::ssl::context::context(boost::asio::ssl::context_base::method)':
/usr/local/include/boost/asio/ssl/impl/context.ipp:93: error: '::SSLv3_method' has not been declared
/usr/local/include/boost/asio/ssl/impl/context.ipp:96: error: '::SSLv3_client_method' has not been declared
/usr/local/include/boost/asio/ssl/impl/context.ipp:99: error: '::SSLv3_server_method' has not been declared
OK jca@

Log message:
Unbreak boost on (at least) alpha, hppa and sparc64
- ensure we don't build the 'context' and 'coroutine' libs, they are not
portable and the latter depends on the former
- don't use the 'gcc_sparc' backend in Boost.atomic, for it doesn't
build; use the generic gcc backend based on __sync_*
- stop tweaking cc -march / -mcpu values; this is not desirable on any
arch and it breaks on sparc64 due to a bogus -mcpu=c3 default
- don't attempt to force -m32 / -m64 flags, this breaks at least alpha
(64 bits but doesn't understand -m64)
alpha, hppa & sparc64 tests by landry@, amd64 bulk by ajacoutot@
ok jasper@

Log message:
don't add -m32 to compiler flags; see if this unbreaks hppa

Log message:
submitted upstream

Log message:
Garbage collect some patches that looks uneeded. Survived a bulk.
If it ends up we have some runtime fallout because of these, we'll fix it and
document the patch.
from Brad (maintainer)
jasper@ had the same diff

Log message:
- update to boost 1.58.0
earlier diff looked good to brad
tested in multiple bulks by aja@ and me
ok aja@ robert@

Log message:
machine/endian.h -> sys/endian.h

Log message:
Remove some chunks of the patch now that _POSIX_VERSION has been
bumped higher.

Log message:
add bzip2 support for boost-iostreams.
needed for future releases of games/wesnoth.
ok brad@ (maintainer)

Log message:
bump after default python version switch

Log message:
- build and install boost_unit_test_framework and friends,
ok aja@

Log message:
- sort lib list

Log message:
- tweak, suggested by fgs@

Log message:
- OpenBSD does not have the definitions for the signals SI_ASYNCIO and
SI_MESGQ.
from markus hennecke
ok landry@

Log message:
- first round of bumps for devel

Log message:
add missing wantlibs, new-style lib_depends/revision, bump

Log message:
build boost with gcc4 and newer libstdc++-v3.
(I'll revisit the math funcs later)

Log message:
fix warning. wesnoth should compile again

Log message:
Add necessary magic to BJAM_CONFIG so that boost honours CFLAGS/CXXFLAGS.
Another funky-build-system bites the dust..

Log message:
Update to boost 1.42, fixes regressions in gzip module introduced in
1.41. Tested without fallout in a bulk build by stephan@, thanks!
Endianess fixes from kili@, mark as NO_REGRESS as regression suite
changed a lot since old previous 1.34 version.
Remove deanna@ from MAINTAINER has she agreed not having time for it atm.
This port doesn't honour CFLAGS but this will be dealt separately.

Log message:
Unbreak boost on hppa, checking for defined(__hppa) to detect HPUX is stupid.
No binary change on other archs, bump PKGNAME to be on the safe side.

Log message:
Fix boost header so that -Werror configure scripts (wesnoth) doesn't
bomb. An update to 1.42 is needed anyway.
ok jasper@

Log message:
delete zero-byte file, pointed out by Brad

Log message:
Add missing patches...

Log message:
Udpate to 1.41.0; original diff from Markus Hennecke

Log message:
- fix patch that didn't apply cleanly. noted by andreas.kahari at gmail.com

Log message:
- revert last commit since gcc3/libstdc++ changes were reverted.

Log message:
- remove hacks to force boost to use threads now that libstdc++ thread
safety has been enabled in gcc3 & libstdc++
- correct detection of thread support in libstdcpp3.hpp
- correct multiple defined T_DIVIDE
- use threads for python.jam
NOTE: this update requires userland to be rebuild with the recent
gcc3/libstdc++ changes. See current.html for instructions.

Log message:
fix atomic_count.hpp: libstdc++ is not built with thread support yet so
adjust atomic_count.hpp to only use libstdc++ when it has been built with
thread support and fall back to using the pthreads implementation.
diagnosed, tested and okay deanna@

Log message:
Security - add fix from boost svn for CVE-2008-0171:
"regex/v4/perl_matcher_non_recursive.hpp in the Boost regex library
(aka Boost.Regex) in Boost 1.33 and 1.34 allows context-dependent
attackers to cause a denial of service (failed assertion and crash)
via an invalid regular expression."
ok naddy@

Log message:
Don't pick up textproc/icu4c.  Problem reported by brad and RD Thrush,
thanks.
no pkg change

Log message:
- unbreak on amd64 by adding -fPIC to the link cmd
tested by sthen@, brad@, eric@ and others, ok brad@ sthen@
- use /dev/urandom (from Brad)

Log message:
Update to boost-1.34.1.
Initial diff from Mikko Tolmunen. Thank you!
Some corrections from brad@.
Tested by deanna@, naddy@, brad@ and myself.
ok deanna@, brad@

Log message:
Build libboost_python.  Ports using it will need to satisfy any python
run depends on their own.  Patch from landry@, change requested by a
few.
And regen patches.
ok landry@

Log message:
Move boost back into a single package.  Splitting it was my mistake.
discussed with many people, "go ahead" steven@

Log message:
Remove quotes surrounding COMMENT*/PERMIT_*/BROKEN

Log message:
Add a patch from Boost CVS for amd64 support in endian.hpp.  From
Jon Olsson <jon at vexed.se>.  Bump pkgnames and order plist.
"looks good" wilfried@

Log message:
base64 distinfo with SHA256

Log message:
The soname needs to match the filename in order for the libs to be
usable.  Noticed by Tero Koskinen, thanks.
Simplify the install by using an undocumented jam rule.
Ok wilfried@.

Log message:
Remove the alpha exception workaround, now that kettenis@ has fixed the
problem.
Ok brad@.

Log message:
Fix this on alpha by disabling the serialization lib.  This lib does
not honor BOOST_NO_EXCEPTIONS, and exception support is currently
broken on alpha.
ok espie@.

Log message:
new MULTI_PACKAGES

Log message:
split into two subpackages, headers and libs, from maintainer

Log message:
zap SCRIPTS_ENV, make sure include files belong to data owner, zap old
SH variable.