Github messages for voidlinux
 help / color / mirror / Atom feed
From: JamiKettunen <JamiKettunen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: boost: update to 1.79.0.
Date: Sat, 27 Aug 2022 21:21:14 +0200	[thread overview]
Message-ID: <20220827192114.CeoN4yWWISFi0hi0LeukUvGV75leova8qvfnFXxnyoE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36204@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 3786 bytes --]

There's a closed pull request on the void-packages repository

boost: update to 1.79.0.
https://github.com/void-linux/void-packages/pull/36204

Description:
[ci skip]

#### Packages to fix (from `xrevshlib boost` as locally build-tested on `x86_64-musl`)
- [x] Aegisub (fails on `do_build()`) - awaiting new upstream release, tip of `dev` branch builds
- [x] PrusaSlicer (fails on `do_build()`) - backported upstream boost 1.79 compile fixes to v2.4.2
- [ ] TSC (fails on `do_build()`)
- [ ] cryfs (fails on `do_build()`)
- [ ] fifengine (fails on `do_build()`)
- [x] uhd (fails on `do_build()`)
  - [ ] gnuradio (failed on `do_build()`, updating to [v3.10.2.0](https://github.com/gnuradio/gnuradio/releases/tag/v3.10.2.0) appears to have disabled building a lot of components including all shared objects and pkg-config files for example, probably just a bunch of missing new "optional" build-time dependencies...)
    - [ ] gnuradio-osmosdr (depends on `gnuradio`)
- [ ] imagescan (fails on `do_build()`)
- [ ] kea (fails on `do_build()`)
- [ ] ledger (fails on `do_build()`)
- [ ] libbitcoin-system (fails on `do_build()`)
  - [ ] libbitcoin-database (depends on `libbitcoin-system`)
    - [ ] libbitcoin-blockchain (depends on `libbitcoin-database`)
      - [ ] libbitcoin-node (depends on `libbitcoin-blockchain`)
      - [ ] libbitcoin-server (depends on `libbitcoin-blockchain`)
  - [ ] libbitcoin-protocol (depends on `libbitcoin-system`)
    - [ ] libbitcoin-client (depends on `libbitcoin-protocol`)
      - [ ] libbitcoin-explorer (depends on `libbitcoin-client`)
  - [ ] libbitcoin-network (depends on `libbitcoin-system`)
- [ ] libetonyek (fails on `do_build()`, appears to need `-std=c++17` or higher? `NUM3Parser.cpp:46:8: error: 'for_each' is not a member of 'std'`)
  - [ ] libreoffice (depends on `libetonyek`)
- [ ] librime (fails on `do_build()`)
- [ ] namecoin (fails on `do_build()`)
- [ ] pulseeffects-legacy (fails on `do_build()`)
- [ ] supercollider (fails on `do_build()`)
- [ ] leatherman (hangs on `do_check()`, test process pinned one core at 100% for 10 minutes)
  - [x] facter (depends on `leatherman`)
- [ ] inkscape (fails on `do_check()`)
- [ ] libtorrent-rasterbar (hangs on `do_check()`, 90/97 test_web_seed_http stuck for 10 minutes)
- [ ] schroot (fails on `do_check()`)
- [ ] bitcoin (fails on `do_check()`)

#### Packages to fix (from `xrevshlib uhd` as locally build-tested on `x86_64-musl`)
- [ ] urh (fails on `do_check()` even after adding `checkdepends="python3-pip"`)

#### Modified patches (boost)
`exec_file.patch`: Removed due to being upstream as https://github.com/boostorg/python/commit/d9f06052e28873037db7f98629bce72182a42410
`mips.patch`: Updated to apply on top of https://github.com/boostorg/fiber/commit/5dc9dabc5d5ff8da53ec897c265c9cba1b6ed0df, not sure if this can be removed now(?)

#### Misc changes
- I've renamed all subpackages of `boost` so that the versioned name doesn't conflict with other numbers and are consistent with the previously existing `boost-python3-1.72`, e.g. `libboost_math_c991.72` is now `libboost_math_c99-1.79` (notice the `-`!)

#### Testing the changes
- I tested the changes in this PR: **NO**

<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!-- 
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


      parent reply	other threads:[~2022-08-27 19:21 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-18 14:28 [PR PATCH] boost: update to 1.79.0.b1 JamiKettunen
2022-03-18 14:32 ` [PR REVIEW] " ahesford
2022-03-18 14:32 ` ahesford
2022-03-18 14:37 ` Johnnynator
2022-03-18 14:38 ` [PR PATCH] [Updated] " JamiKettunen
2022-03-18 16:32 ` JamiKettunen
2022-03-18 16:33 ` [PR REVIEW] " JamiKettunen
2022-03-18 16:42 ` [PR PATCH] [Updated] " JamiKettunen
2022-03-18 17:58 ` JamiKettunen
2022-03-18 23:32 ` JamiKettunen
2022-03-18 23:33 ` JamiKettunen
2022-03-19 12:39 ` JamiKettunen
2022-04-08  3:00 ` q66
2022-05-04 15:22 ` loreb
2022-05-26 15:22 ` [PR PATCH] [Updated] " JamiKettunen
2022-05-26 15:29 ` [PR PATCH] [Updated] boost: update to 1.79.0 JamiKettunen
2022-05-26 16:21 ` JamiKettunen
2022-05-26 18:41 ` JamiKettunen
2022-05-26 20:27 ` JamiKettunen
2022-05-26 20:29 ` JamiKettunen
2022-05-27 16:20 ` JamiKettunen
2022-05-27 16:21 ` JamiKettunen
2022-06-08 22:18 ` JamiKettunen
2022-06-08 23:46 ` JamiKettunen
2022-06-08 23:47 ` JamiKettunen
2022-06-09  0:26 ` JamiKettunen
2022-07-06 11:26 ` atweiden
2022-08-27  3:35 ` classabbyamp
2022-08-27 19:21 ` JamiKettunen
2022-08-27 19:21 ` JamiKettunen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220827192114.CeoN4yWWISFi0hi0LeukUvGV75leova8qvfnFXxnyoE@z \
    --to=jamikettunen@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).