From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: 71837-done@debbugs.gnu.org
Subject: [bug#71837] [PATCH] gnu: clasp: Prevent ID clashes in dependent packages.
Date: Sun, 07 Jul 2024 08:21:35 +0200 [thread overview]
Message-ID: <780aee2f1c0e5177206cc929ce1525285e2e435f.camel@gmail.com> (raw)
In-Reply-To: <b96419e97552f3d3adb69815563b32024eb9d083.1719644448.git.liliana.prikler@gmail.com>
Am Samstag, dem 29.06.2024 um 08:53 +0200 schrieb Liliana Marie
Prikler:
> Clasp uses an interesting CRTP pattern to insert statically (i.e.
> compile-time) generated numeric IDs into global fields. However,
> these templates are instantiated once per shared library---thus,
> whenever a library is linked, new IDs are generated, and the original
> intent (safely type-casting objects across libraries) is lost. To
> help the linker out, we make sure that these IDs are only
> instantiated in clasp and not when building other libraries.
>
> * gnu/packages/patches/clasp-hide-event-ids.patch: New file.
> * gnu/local.mk (dist_patch_DATA): Register it here.
> * gnu/packages/clasp.scm (source)[patches]: Add it here.
> (clingo)[#:phases]: Drop ‘skip-failing-tests’.
> (python-clorm)[#:phases]<fix-breaking-tests>: Adjust accordingly.
> (python-clintest): Drop arguments.
> ---
Looks like I got my patch IDs messed up somehow.
Anyhow, this is pushed.
prev parent reply other threads:[~2024-07-07 6:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-29 6:53 [bug#71837] [PATCH] gnu: clasp: Prevent ID clashes in dependent packages Liliana Marie Prikler
2024-06-29 8:51 ` [bug#71837] [PATCH v2 1/3] gnu: libadwaita: Update to 1.5.2 Liliana Marie Prikler
2024-06-29 8:51 ` [bug#71837] [PATCH v2 3/3] gnu: komikku: Update to 1.46.0 Liliana Marie Prikler
2024-07-07 6:17 ` bug#71837: " Liliana Marie Prikler
2024-07-07 6:22 ` bug#71839: " Liliana Marie Prikler
2024-07-03 4:24 ` [bug#71837] [PATCH v2 2/3] gnu: webp-pixbuf-loader: Update to 0.2.4 Liliana Marie Prikler
2024-07-07 6:21 ` Liliana Marie Prikler [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=780aee2f1c0e5177206cc929ce1525285e2e435f.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=71837-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.