public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ludo at gnu dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug guile/28994] [build] Werror=deprecated-declarations for scm_install_gmp_memory_functions
Date: Mon, 09 May 2022 08:35:50 +0000 [thread overview]
Message-ID: <bug-28994-4717-JFl2s2rwWC@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28994-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28994
--- Comment #3 from Ludovic Courtès <ludo at gnu dot org> ---
Hi,
(In reply to Tom Tromey from comment #1)
> Probably more of a guile thing than a build thing.
> I assume some porting work is required for 3.0?
'scm_install_gmp_memory_functions' is deprecated in Guile 3.0.8 (not 3.0.7),
because Guile 3.0.8 no longer relies on custom GMP allocators; thus, setting
this variable doesn't have any effect.
The variable will remain for the whole 3.0.x series so I'd recommend
-Wno-error=deprecated-declarations or a pragma to the same effect.
Thoughts?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-05-09 8:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 14:12 [Bug build/28994] New: " vries at gcc dot gnu.org
2022-04-15 13:39 ` [Bug guile/28994] " tromey at sourceware dot org
2022-05-07 14:58 ` tromey at sourceware dot org
2022-05-08 6:37 ` vries at gcc dot gnu.org
2022-05-09 8:35 ` ludo at gnu dot org [this message]
2022-05-12 22:27 ` tromey at sourceware dot org
2022-07-06 8:02 ` vries at gcc dot gnu.org
2022-07-06 14:04 ` ludo at gnu dot org
2022-07-06 15:16 ` vries at gcc dot gnu.org
2022-07-07 7:59 ` vries at gcc dot gnu.org
2022-07-07 13:52 ` ludo at gnu dot org
2022-07-08 14:02 ` vries at gcc dot gnu.org
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=bug-28994-4717-JFl2s2rwWC@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).