From: Leo Famulari <leo@famulari.name>
To: 72040-done@debbugs.gnu.org
Subject: bug#72040: [core-updates] Boost bug / breaks libreoffice [was libetonyek link failure]
Date: Wed, 24 Jul 2024 17:48:12 -0400 [thread overview]
Message-ID: <ZqF2nFjdbKNQl_-Z@jasmine.lan> (raw)
In-Reply-To: <ZpA_Leh5av2htGYT@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 731 bytes --]
On Thu, Jul 11, 2024 at 04:23:09PM -0400, Leo Famulari wrote:
> Subject: [PATCH] WIP: Boost: Fix a bug that breaks libetonyek.
>
> This fixes <https://issues.guix.gnu.org/72040>
>
> * gnu/packages/patches/boost-fix-duplicate-definitions-bug.patch: New file.
> * gnu/local.mk (dist_patch_DATA): Add it.
> * gnu/packages/boost.scm (boost)[source]: Use it.
> (boost-for-source-highlight): New variable, not using the patch.
> * gnu/packages/pretty-print.scm (source-highlight)[inputs]: Replace BOOST with
> BOOST-FOR-SOURCE-HIGHLIGHT.
Pushed as 1ab3e3b26fdc43d48826119d4f51379571dd89b6 along with a followup
patch that fixes another problem with Libreoffice. With these changes,
we have Libreoffice on core-updates.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-07-24 21:49 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
2024-07-13 17:40 ` Leo Famulari
2024-07-24 21:48 ` Leo Famulari [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=ZqF2nFjdbKNQl_-Z@jasmine.lan \
--to=leo@famulari.name \
--cc=72040-done@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.