| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Release notes: https://www.boost.org/users/history/version_1_85_0.html
|
|
|
|
boost184: init at 1.84.0
|
|
|
|
|
|
Add ucrt64 mingw toolchain.
|
|
boost183: init at 1.83.0
|
|
msvcrt is only one of the libcs in MinGW. We therefore
replace explictly testing for msvcrt with the isMinGW
predicate. This lays the foundation for ucrt64 support.
|
|
amjoseph-nixpkgs/pr/boost/move-mipsN32-to-badPlatforms
|
|
|
|
Presence in meta.badPlatforms can be tested with
lib.meta.availableOn, but meta.broken cannot.
I use this to compile as much of my routers' userspace as possible
for Mips64n32, and to automatically detect the few binaries (mostly
those which use boost) cannot and build those for Mips64n64.
|
|
ref. https://github.com/boostorg/python/commit/a218babc8daee904a83f550fb66e5cb3f1cb3013
Co-authored-by: Theodore Ni <3806110+tjni@users.noreply.github.com>
|
|
boost{175,176,177,178,179,180}: clang 16 and libc++ 15 fixes
|
|
Clang 16 began diagnosing ill-formed constant expressions for values
outside the range of enums without a fixed underlying type. While the
error can be suppressed, it will become a hard error in clang 17.
|
|
libc++ 15 dropped support for `std::unary_function` and
`std::binary_function` in C++17 and C++20. C++17 is the default for
clang 16, but clang 15 is also affected in those language modes.
This incompatibility is fixed in Boost 1.81, but the late patch for
Boost 1.80 applies to earlier versions and allows those versions to
build with clang 16 (and clang 15 in the affected modes).
|
|
|
|
|
|
|
|
|
|
|
|
Co-authored-by: Weijia Wang <9713184+wegank@users.noreply.github.com>
|
|
The boost iostreams library supports zstd and lzma compression if it can
find the packages: https://www.boost.org/doc/libs/1_79_0/libs/iostreams/doc/installation.html
|
|
|
|
|
|
|
|
|
|
This makes it easier to disable ICU support with `override`, where
the closure size matters.
|
|
Explicitly tell Boost where to find Python, so Boost.Python can build be cross-
compiled.
|
|
|
|
|
|
The explanation for the conditional introduced by
61d9f201baeef4c4bb91ad8a8f5f89b747e0dfe4 is longer than a reasonable
inline comment should be. It directed the reader to use `git blame`,
but that tends to bitrot. Let's point the user to a specific nixpkgs
git hash.
This commit cannot be squashed into the previous commit, because a
commit cannot mention its own commit-hash (without performaing an
expensive double-sha1 preimage attack, of course).
|
|
boost-context changed its name for mips from "mips1" to "mips" in this
commit:
https://github.com/boostorg/context/commit/6edc8184a7136de4603a6f903d9b9b864ca9cf57
however the native-build code to detect the local architecture still
reports "mips1":
https://github.com/boostorg/boost/blob/67c074b249538cf441724f9bbb3929d0f6b4f333/boostcpp.jam#L637
Therefore native builds of boost-context on mips must specify
architecture= explicitly; without this you will get link failures
"undefined reference to `jump_fcontext`" in code that uses
boost-context.
Currently the "cross compile" codepath, which provides explicit
architecture/abi/address-model/binary-format/os parameters, is
prefixed by this comment:
```
# TODO: make this unconditional
```
This commit does so, at least if `isMips`.
This commit is needed in order for native builds of nix to succeed on
mips.
|
|
|
|
boost: support s390x
|
|
s390x will return s390 as its cpu family,
but boost does not have generic s390 support, only s390x.
Add a special case to build for s390x architecture
|
|
PCH breaks the build when cross-compiling from darwin to linux.
Should fix a good number of our cross-trunk hydra builds.
|
|
|
|
|
|
|
|
|
|
See https://www.boost.org/users/news/boost_has_moved_downloads_to_jfr.html
for more info
|
|
|
|
|
|
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
|
|
This commit makes two changes:
1. Boost changed its taxonomy for architecture names between the 1.77 and
1.78 releases, in this commit:
https://github.com/boostorg/context/commit/6edc8184a7136de4603a6f903d9b9b864ca9cf57
2. During the review of #161162 I [was asked about][1] the source of
the [mips64-context.patch][2] that I had included in the original
version of the PR. I searched through the boost-context revision
history and found [a nearly identical patch][3], which I
substituted in the final, merged version of the PR.
As it turns out, my [mips64-context.patch][2] was an earlier
revision of what was eventually accepted to boost-context. The
only difference between the two patches is the name they use:
mips64 vs mips1.
When switching to the accepted version of the boost patch, I should
have also updated libraries/boost/generic.nix to change mips64 to
mips1. This commit does that.
[1]: https://github.com/NixOS/nixpkgs/pull/161162#discussion_r847903087
[2]: https://raw.githubusercontent.com/a-m-joseph/nixpkgs/1ca5025945470ce96408552b9117674b12efaf04/pkgs/development/libraries/boost/mips64-context.patch
[3]: https://github.com/boostorg/context/commit/e3f744a1862164062d579d1972272d67bdaa9c39.patch
|
|
Co-authored-by: Sandro <sandro.jaeckel@gmail.com>
|
|
Prior needsUserConfig setting is unconditionally applied for darwin.
This is not valid for static builds and should only be set for dynamically linked darwin builds.
|
|
This was merged to `staging` already, but that's just unnecessary delay
after the PR was amended not to change boost defaults.
|
|
|
|
|
