unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: 72040@debbugs.gnu.org
Subject: bug#72040: [core-updates] Boost bug / breaks libreoffice [was libetonyek link failure]
Date: Sat, 13 Jul 2024 13:39:21 -0400	[thread overview]
Message-ID: <ZpK7yfHwapBPlkaM@jasmine.lan> (raw)
In-Reply-To: <ZpA_Leh5av2htGYT@jasmine.lan>

On Thu, Jul 11, 2024 at 04:23:09PM -0400, Leo Famulari wrote:
> Here's a patch that patches Boost, while also creating a hidden package
> boost-for-source-highlight. This variant is only used by the
> source-highlight package, which is used by gdb, and thus rust. So, it
> aims to avoid rebuilding everything rust.

Here's an updated patchset that builds on the previous patch.

It patches Boost to fix the bug, creates the Boost variant for
source-highlight / gdb / Rust, and then finally fixes a missing
dependency failure in Libreoffice.

It does cause several thousand rebuilds (5933 rebuilds), but much fewer than if we did
not avoid changing the source-highlight derivation (15383 rebuilds).

There is some discussion on the Libreoffice mailing list, but so far
it's inconclusive from my perspective. But if I understand correctly,
their recommended solution would be to create a source origin of
Boost >=1.84, copy that into the Libreoffice and libetonyek source
trees, and build the programs against that "internal" Boost. I'm not
sure that's better than simply updating Boost.




  reply	other threads:[~2024-07-13 17:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-10 17:33 bug#72040: [core-updates] libetonyek link failure Leo Famulari
2024-07-11 16:00 ` Leo Famulari
2024-07-11 16:41   ` Leo Famulari
2024-07-11 19:15     ` bug#72040: [core-updates] Boost bug / breaks libreoffice [was libetonyek link failure] Leo Famulari
2024-07-11 20:23       ` Leo Famulari
2024-07-13 17:39         ` Leo Famulari [this message]
2024-07-13 17:40           ` Leo Famulari
2024-07-24 21:48         ` Leo Famulari

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=ZpK7yfHwapBPlkaM@jasmine.lan \
    --to=leo@famulari.name \
    --cc=72040@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).