Commit Graph

292 Commits

Author SHA1 Message Date
Artturi
d78d760dae
Merge pull request #245300 from amjoseph-nixpkgs/pr/boost/move-mipsN32-to-badPlatforms 2023-09-08 01:32:00 +03:00
Adam Joseph
4a032b19fc boost: move isMips64n32 from meta.broken to meta.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.
2023-07-24 21:27:39 -07:00
Guilhem Saurel
9f9b8a0733 boost: fix for python 3.11
ref. a218babc8d

Co-authored-by: Theodore Ni <3806110+tjni@users.noreply.github.com>
2023-07-14 09:43:16 +02:00
Weijia Wang
fe35cda7f9
Merge pull request #240642 from reckenrode/boost-clang16
boost{175,176,177,178,179,180}: clang 16 and libc++ 15 fixes
2023-06-30 17:15:06 +03:00
Randy Eckenrode
cec7b5e87c
boost{175,176,177,178,179,180}: fix build with clang 16
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.
2023-06-29 23:32:02 -04:00
Randy Eckenrode
e3323ac20c
boost{175,176,177,178,179,180}: fix build with libc++ 15+
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).
2023-06-29 23:32:02 -04:00
Uri Baghin
e1b4124f0a boost: fix cross compilation for darwin hosts 2023-06-22 15:33:54 +10:00
Weijia Wang
3c0a8a7dfd boost: cleanup 2023-06-12 14:41:05 +03:00
Nicolas Benes
a30bcb5d38 boost: Remove references to unsupported versions 2023-05-07 21:46:34 +02:00
Nicolas Benes
61e3deefae boost166: remove unused pkg 2023-05-07 18:38:50 +02:00
Nicolas Benes
c72178cf2b boost165: remove unused pkg 2023-05-07 18:38:32 +02:00
Alexis Hildebrandt
e73da62a1d boost182: init at 1.82.0
Co-authored-by: Weijia Wang <9713184+wegank@users.noreply.github.com>
2023-04-25 09:36:51 +02:00
Bouke van der Bijl
ab04f4777b boost: add zstd and lzma support
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
2023-02-02 10:55:16 +01:00
Shawn8901
a59dda942c treewide: remove global with lib; statements in pkgs/development 2023-01-26 18:31:02 +01:00
Sandro
1292c04563
Merge pull request #208210 from wegank/boost-181-init 2023-01-08 23:47:46 +01:00
Weijia Wang
436c5f8dc2 boost159, boost160: drop 2023-01-01 22:16:22 +01:00
Weijia Wang
6463ec06e3 boost181: init at 1.81.0 2022-12-29 10:29:26 +01:00
oxalica
06c0cce0e5 boost: add configurable enableIcu flag
This makes it easier to disable ICU support with `override`, where
the closure size matters.
2022-12-09 02:56:38 +08:00
Ben Wolsieffer
aa1b96ff78 boost: enable cross-compiling Boost.Python
Explicitly tell Boost where to find Python, so Boost.Python can build be cross-
compiled.
2022-11-11 17:29:53 -05:00
Alex Wied
aa473065cb boost180: init at 1.80.0 2022-10-24 15:01:47 -04:00
github-actions[bot]
aac580f88f
Merge master into staging-next 2022-10-20 00:05:13 +00:00
Adam Joseph
2df2b52806 boost/generic.nix: reference commit-hash in comment
The explanation for the conditional introduced by
61d9f201ba 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).
2022-10-19 20:22:45 +02:00
Adam Joseph
ac92b409b3 boost: if isMips use the "cross compile" codepath unconditionally
boost-context changed its name for mips from "mips1" to "mips" in this
commit:

  6edc8184a7

however the native-build code to detect the local architecture still
reports "mips1":

  67c074b249/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.
2022-10-19 20:22:45 +02:00
github-actions[bot]
ab4849492d
Merge master into staging-next 2022-10-17 06:24:16 +00:00
Ryan Burns
8b08189c61
Merge pull request #196244 from r-burns/boost-s390x
boost: support s390x
2022-10-16 22:48:36 -07:00
Ryan Burns
cc390e2ded 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
2022-10-16 00:25:31 -07:00
Ryan Burns
bbe814352f boost: disable pch for darwin -> linux cross
PCH breaks the build when cross-compiling from darwin to linux.
Should fix a good number of our cross-trunk hydra builds.
2022-10-14 17:10:57 -07:00
Martin Weinelt
195aa5887d
boost: fix build with enablePython by passing libxcrypt 2022-10-09 18:14:36 +02:00
github-actions[bot]
48a7b8564d
Merge staging-next into staging 2022-09-01 06:07:49 +00:00
Nicolas Benes
9a3d274dd6 boost155: remove 2022-08-31 18:50:53 +02:00
Yves Fischer
9e77929f19 boost: allow enablePython in cross compilation 2022-08-25 23:26:51 +02:00
Pavol Rusnak
1aa1cf03b6 boost: use jfrog mirror instead of bintray
See https://www.boost.org/users/news/boost_has_moved_downloads_to_jfr.html
for more info
2022-06-20 19:04:03 +02:00
Alex Wied
8d8327c1cc boost179: init at 1.79.0 2022-05-12 10:43:06 -04:00
Andrew Childs
de396a3c0a boost159: fix build on aarch64-darwin 2022-05-08 22:22:22 +03:00
Anders Kaseorg
6920d8ca42 treewide: Simplify negated uses of versionAtLeast, versionOlder
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
2022-04-25 13:35:24 -07:00
Adam Joseph
5952698e53 boost: fix taxonomy mistake, account taxonomy change in v1.78
This commit makes two changes:

1. Boost changed its taxonomy for architecture names between the 1.77 and
   1.78 releases, in this commit:

   6edc8184a7

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]: e3f744a186.patch
2022-04-13 21:56:44 -07:00
Adam Joseph
1c51548468 boost: support for cross-compiling boost to a mips64 target
Co-authored-by: Sandro <sandro.jaeckel@gmail.com>
2022-04-12 15:21:43 -07:00
Doro Rose
4a8f46f7ce boost: make boost work for static darwin builds
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.
2022-04-10 20:51:12 +02:00
Vladimír Čunát
a1c53b6cdd
Merge #161568: boost178: init at 1.78.0
This was merged to `staging` already, but that's just unnecessary delay
after the PR was amended not to change boost defaults.
2022-04-10 10:56:13 +02:00
wheelsandmetal
4de2c2a00c boost178: init at 1.78.0 2022-03-31 12:36:50 +01:00
github-actions[bot]
c6dd9fd65d
Merge master into staging-next 2022-03-25 18:01:14 +00:00
maralorn
0e0bb200ff
Merge pull request #165327 from ncfavier/fetchpatch-relative
fetchpatch: add `preIncludes` and `relative`
2022-03-25 16:32:14 +01:00
Naïm Favier
a6bc988f00
boost177: use fetchpatch's relative argument
We can drop `includes` since there's only one file in that directory.
2022-03-25 10:47:12 +01:00
github-actions[bot]
c80dabe3b1
Merge staging-next into staging 2022-03-23 06:01:55 +00:00
Markus Wamser
713648a19b
boost: unbreak build for 1.65 and 1.66 (#163216)
Co-authored-by: Sandro <sandro.jaeckel@gmail.com>
2022-03-23 03:51:12 +01:00
Maximilian Bosch
f363b7c5df
boost1{69,70,72}: fix build w/glibc-2.34
To quote the release-notes[1]:

> When _DYNAMIC_STACK_SIZE_SOURCE or _GNU_SOURCE are defined,
> PTHREAD_STACK_MIN is no longer constant and is redefined to
> sysconf(_SC_THREAD_STACK_MIN).  This supports dynamic sized register
> sets for modern architectural features like Arm SVE.

This basically means that if the above applies, `#if PTHREAD_STACK_MIN > 0`
won't compile anymore because `PTHREAD_STACK_MIN` isn't a hard-coded
number, but `__sysconf (__SC_THREAD_STACK_MIN_VALUE)`[2].

The issue (for 1.69, 1.70, 1.72 - the other versions seem OK) was
reported upstream, but only for Solaris[3], however the corresponding
patches[4] seem to work as well for us.

Failing Hydra build: https://hydra.nixos.org/build/150926294

[1] https://sourceware.org/pipermail/libc-alpha/2021-August/129718.html
[2] See `${pkgs.glibc.dev}/include/bits/pthread_stack_min-dynamic.h`
[3] https://github.com/boostorg/thread/issues/283
[4] https://github.com/conan-io/conan-center-index/pull/361
2022-02-27 10:25:35 +01:00
Ryan Burns
c827d9df00
Merge pull request #153143 from r-burns/boost-no-atomics
[staging] boost177: fix on platforms without atomics
2022-02-16 18:55:03 -08:00
Andrew Childs
8668f940c5
boost: refine assertion requiring pth support in clang (#159990)
The pth feature was only used by boost's build with clang on linux,
and should not prevent building on darwin.
2022-02-14 22:02:36 -05:00
Ryan Burns
b906464824 boost177: fix on platforms without atomics
backport patch from boost178 to fix compilation when atomics are not available,
e.g. for armv5tel
2021-12-31 21:00:21 -08:00
Alyssa Ross
f404068903
Merge remote-tracking branch 'nixpkgs/staging-next' into staging
Conflicts:
	pkgs/servers/search/groonga/default.nix
2021-12-02 14:52:44 +00:00