summary refs log tree commit diff
path: root/pkgs/development/libraries/boost
Commit message (Collapse)AuthorAge
* boost: *Flags are listsRobin Gloster2019-12-30
|
* boost : extra arguments to b2Pulkit Sinha2019-11-29
| | | | | | | | Certain boost features require compile time flags. For example - https://www.boost.org/doc/libs/1_71_0/libs/test/doc/html/boost_test/adv_scenarios/obsolete_init_func.html https://www.boost.org/doc/libs/1_71_0/libs/test/doc/html/boost_test/utf_reference/link_references/link_boost_test_no_main.html https://www.boost.org/doc/libs/1_71_0/libs/test/doc/html/boost_test/utf_reference/link_references/link_boost_test_dyn_link.html This commit add the ability to specify arbitrary extra arguments to b2's arguments.
* Merge pull request #67282 from dtzWill/feature/boost-1.71Will Dietz2019-11-16
|\ | | | | boost171: init at 1.71.0
| * boost171: use 'urls' attribute per suggestion (thanks!)Will Dietz2019-09-03
| | | | | | Co-Authored-By: Jon <jonringer@users.noreply.github.com>
| * boost171: grab from bintray, not on sf.net ("yet"?)Will Dietz2019-08-22
| |
| * boost171: init at 1.71.0Will Dietz2019-08-22
| |
* | treewide: remove redundant recvolth2019-08-28
|/
* treewide: remove unused variables (#63177)volth2019-06-16
| | | | | | * treewide: remove unused variables * making ofborg happy
* Merge branch 'staging-next' into stagingVladimír Čunát2019-05-26
|\
| * Merge pull request #59754 from matthewbauer/remove-old-patchesMatthew Bauer2019-05-18
| |\ | | | | | | Cleanup; Remove old patches
| | * boost: remove old cygwin patchesMatthew Bauer2019-04-16
| | | | | | | | | | | | Most of these are unused and the others only used in 1.59.
* | | boost: run build and install hooksBenjamin Hipple2019-05-24
|/ / | | | | | | | | Users who want to patch boost may put a postInstall hook in an overlay, which requires that that expression runs them on the buildPhase and installPhase.
* | Merge master into staging-nextFrederik Rietdijk2019-05-07
|\ \
| * \ Merge pull request #59602 from amirshavit/boost170Peter Simons2019-05-06
| |\ \ | | | | | | | | boost 170: init at 1.70.0
| | * | boost170: init at 1.70.0Amir Shavit2019-04-15
| | | |
* | | | treewide: mark bad packagesMatthew Bauer2019-04-26
| | | | | | | | | | | | | | | | Some old stuff is known not to work.
* | | | boost167: patch for macOS 10.12Dmitry Kalinkin2019-04-26
|/ / /
* | / boost: fix 1.55 build on macOS (#59508)strager2019-04-16
| |/ |/| | | | | | | darwin-no-system-python.patch does not apply cleany on Boost 1.55's sources. Fix this patch file for Boost 1.55, making it build successfully on macOS.
* | boost: fix misspelled version numbers in 1.66.0, 1.67.0, 1.68.0, and 1.69.0Peter Simons2019-03-06
| |
* | treewide: remove wkennington as maintainerJörg Thalheim2019-01-26
|/ | | | | | He prefers to contribute to his own nixpkgs fork triton. Since he is still marked as maintainer in many packages this leaves the wrong impression he still maintains those.
* Merge pull request #51813 from samueldr/aarch64/disable-non-arm-builds-part-1Samuel Dionne-Riel2018-12-20
|\ | | | | aarch64: ZHF for aarch64 (1/??)
| * boost: Fixes disabling for aarch64-linux for <1.59Samuel Dionne-Riel2018-12-10
| | | | | | | | | | | | | | | | | | Between 2b450377bf6e51cce0d831a88e74d5f61811b74d and the current revision, the semantics behind "platforms" changed, and removing the "aarch64-linux" string doesn't work anymore to filter it out. Instead, blacklist the platform using the (comparatively) new badPlatforms.
* | boost169: init (at 1.69)Will Dietz2018-12-16
|/
* boost: use correct c compiler for bootstrappingMatthew Bauer2018-10-17
| | | | we need a c compiler that runs on the build machine for boost to work
* treewide: preserve hashesMatthew Bauer2018-10-16
| | | | avoid mass rebuild from the last commits
* boost: use correct platformMatthew Bauer2018-10-16
| | | | | | "platforms.all" could include any possible os (even a machine with no OS at all!). We can’t possible hope to support all of that, so need to be more specific.
* boost: remove broken patchMatthew Bauer2018-10-16
| | | | the boost url is broken - remove for now
* boost: fix fiber header (#47540)Milan Svoboda2018-10-01
| | | | | include/boost/fiber/detail/context_spmc_queue.hpp:1:1: error: stray ‘\357’ in program caused by a leftover UTF-8 Byte Order Mark
* boost: limit concurrent jobs to the maximum supported number (#47255)Andrew Dunham2018-09-24
|
* Merge branch 'master' into stagingVladimír Čunát2018-09-01
|\ | | | | | | A few trivial conflicts due to *Platforms mass replace.
| * treewide: Remove usage of remaining redundant platform compatability stuffJohn Ericson2018-08-30
| | | | | | | | | | Want to get this out of here for 18.09, so it can be deprecated thereafter.
* | boost: disable python explicitly in b2Args (#45679)Stephen2018-08-28
|/ | | | (cherry picked from commit 3b862a638952c814c49291ca3efa13e8363c77a2)
* boost168: initWill Dietz2018-08-22
| | | | Drop patch from 1.67 that's already included.
* Merge staging-next into master (#44009)Frederik Rietdijk2018-07-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * substitute(): --subst-var was silently coercing to "" if the variable does not exist. * libffi: simplify using `checkInputs` * pythonPackges.hypothesis, pythonPackages.pytest: simpify dependency cycle fix * utillinux: 2.32 -> 2.32.1 https://lkml.org/lkml/2018/7/16/532 * busybox: 1.29.0 -> 1.29.1 * bind: 9.12.1-P2 -> 9.12.2 https://ftp.isc.org/isc/bind9/9.12.2/RELEASE-NOTES-bind-9.12.2.html * curl: 7.60.0 -> 7.61.0 * gvfs: make tests run, but disable * ilmbase: disable tests on i686. Spooky! * mdds: fix tests * git: disable checks as tests are run in installcheck * ruby: disable tests * libcommuni: disable checks as tests are run in installcheck * librdf: make tests run, but disable * neon, neon_0_29: make tests run, but disable * pciutils: 3.6.0 -> 3.6.1 Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/pciutils/versions. * mesa: more include fixes mostly from void-linux (thanks!) * npth: 1.5 -> 1.6 minor bump * boost167: Add lockfree next_prior patch * stdenv: cleanup darwin bootstrapping Also gets rid of the full python and some of it's dependencies in the stdenv build closure. * Revert "pciutils: use standardized equivalent for canonicalize_file_name" This reverts commit f8db20fb3ae382eba1ba2b160fe24739f43c0bd7. Patching should no longer be needed with 3.6.1. * binutils-wrapper: Try to avoid adding unnecessary -L flags (cherry picked from commit f3758258b8895508475caf83e92bfb236a27ceb9) Signed-off-by: Domen Kožar <domen@dev.si> * libffi: don't check on darwin libffi usages in stdenv broken darwin. We need to disable doCheck for that case. * "rm $out/share/icons/hicolor/icon-theme.cache" -> hicolor-icon-theme setup-hook * python.pkgs.pytest: setupHook to prevent creation of .pytest-cache folder, fixes #40273 When `py.test` was run with a folder as argument, it would not only search for tests in that folder, but also create a .pytest-cache folder. Not only is this state we don't want, but it was also causing collisions. * parity-ui: fix after merge * python.pkgs.pytest-flake8: disable test, fix build * Revert "meson: 0.46.1 -> 0.47.0" With meson 0.47.0 (or 0.47.1, or git) things are very wrong re:rpath handling resulting in at best missing libs but even corrupt binaries :(. When we run patchelf it masks the problem by removing obviously busted paths. Which is probably why this wasn't noticed immediately. Unfortunately the binary already has a long series of paths scribbled in a space intended for a much smaller string; in my testing it was something like lengths were 67 with 300+ written to it. I think we've reported the relevant issues upstream, but unfortunately it appears our patches are what introduces the overwrite/corruption (by no longer being correct in what they assume) This doesn't look so bad to fix but it's not something I can spend more time on at the moment. -- Interestingly the overwritten string data (because it is scribbled past the bounds) remains in the binary and is why we're suddenly seeing unexpected references in various builds -- notably this is is the reason we're seeing the "extra-utils" breakage that entirely crippled NixOS on master (and probably on staging before?). Fixes #43650. This reverts commit 305ac4dade5758c58e8ab1666ad0197fd305828d. (cherry picked from commit 273d68eff8f7b6cd4ebed3718e5078a0f43cb55d) Signed-off-by: Domen Kožar <domen@dev.si>
* boost: disable system Python.framework detectionDaiderd Jordan2018-07-03
| | | | | | | There doesn't seem to be a --without-python flag and since the system framework is always available the build tries to enable python support while we have it disabled by default and explicitly don't pass in the python headers.
* boost: Disable Python / Numpy support by defaultEelco Dolstra2018-07-01
| | | | | We can't have a C++ library pulling in Numpy and its gazillion dependencies by default.
* boost: use standardized system informationMatthew Bauer2018-06-23
|
* boost: use default toolset optionMatthew Bauer2018-06-23
| | | | | | | | for 1.66 & 1.67 we were overriding the default toolset option. This meant that gcc-cross was not being selected properly, breaking the cross toolchain. /cc @dtzWill
* boost 1.67 (#41258)Will Dietz2018-06-03
|
* boost: Fix static library builds. (link=static and runtime-link=static ↵tkatchev2018-03-22
| | | | together breaks Boost's build scripts.)
* boost: Fix cross-compilationShea Levy2018-02-28
|
* boost: Don't store absolute path in #lineEelco Dolstra2018-02-05
| | | | | | | This causes packages to have boost.dev in their runtime closures, via assertion messages. Fixes #34462.
* Correct boost configure phase when enablePython is falseBojan Nikolic2018-01-03
| | | | | The bootstrap script does not seem to have --without-python; instead just omit --with-python option
* boost: Do not force numpy support from 1.65Bojan Nikolic2018-01-02
| | | | | | | | | | | | | The reason is that if cross compiling (or for other reasons) python bindings as a whole are turned off. Those two lines then trigger assertion errors unless manually overridden for cross compilation. This way: 1. The `enableNumpy` default respects the `enablePython deafult. 2. Cross works by default 3. Absurd manual overrides still break as they should 4. The `>= 1.65` logic is direct and not a maintaince gotcha.
* Merge pull request #33188 from obsidiansystems/clean-boostJohn Ericson2017-12-30
|\ | | | | boost: Clean, reducing duplication
| * boost: Clean, reducing duplicationJohn Ericson2017-12-30
| | | | | | | | | | | | This was motivated originally by my cross work, but that goal requires a few more commits to other things. Still, it's good to start the cleanup now / get things out of the way.
* | boost165: make it possible to build without numpyFrederik Rietdijk2017-12-22
| |
* | boost166: init at 1.66.0Tristan Carel2017-12-22
|/
* boost: build Python numpy extension by defaultTristan Carel2017-12-12
| | | | | In order to manipulate Python arrays numpy is needed from boost 1.65 on. http://www.boost.org/users/history/version_1_65_1.html
* treewide: Use `targetPrefix` instead of `prefix` for platform name prefixesJohn Ericson2017-11-27
| | | | | | | | | Certain tools, e.g. compilers, are customarily prefixed with the name of their target platform so that multiple builds can be used at once without clobbering each other on the PATH. I was using identifiers named `prefix` for this purpose, but that conflicts with the standard use of `prefix` to mean the directory where something is installed. To avoid conflict and confusion, I renamed those to `targetPrefix`.
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-06-21 04:30:31 +0000