From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Cc: "Ludovic Courtès" <ludo@gnu.org>
Subject: [committed][gdb/build] Handle deprecation of scm_install_gmp_memory_functions
Date: Fri, 8 Jul 2022 16:03:05 +0200 [thread overview]
Message-ID: <ead1dbfe-3489-4739-735b-ea2325c7323a@suse.de> (raw)
In-Reply-To: <20220707075809.GA16313@delia>
On 7/7/22 09:58, Tom de Vries wrote:
> Hi,
>
> When building gdb with guile 3.0.8, we run into:
> ...
> gdb/guile/guile.c: In function \
> 'void gdbscm_initialize(const extension_language_defn*)':
> gdb/guile/guile.c:680:5: error: 'scm_install_gmp_memory_functions' is \
> deprecated [-Werror=deprecated-declarations]
> 680 | scm_install_gmp_memory_functions = 0;
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> In file included from /usr/include/guile/3.0/libguile.h:128,
> from gdb/guile/guile-internal.h:30,
> from gdb/guile/guile.c:36:
> /usr/include/guile/3.0/libguile/deprecated.h:164:20: note: declared here
> 164 | SCM_DEPRECATED int scm_install_gmp_memory_functions;
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> cc1plus: all warnings being treated as errors
> make[1]: *** [Makefile:1896: guile/guile.o] Error 1
> ...
>
> The variable has been deprecated because it no longer has any effect.
>
> Fix this by disabling the specific deprecation warning.
>
> Also handle upcoming guile versions > 3.0, in which the variable will be
> removed, by limiting the usage of the variable to guile versions <= 3.0.
>
> This does not break anything. The variable was merely used to address a
> problem present in guile versions <= v3.0.5.
>
> Note that we don't limit the usage of the variable to guile versions <= 3.0.5,
> because we want to support f.i. building against 3.0.6 and then using a shared
> lib with 3.0.5.
>
> Tested on x86_64-linux.
>
> Co-Authored-By: Tom de Vries <tdevries@suse.de>
>
> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=28994
>
> Any comments?
>
Committed.
Thanks,
- Tom
> [gdb/build] Handle deprecation of scm_install_gmp_memory_functions
>
> ---
> gdb/guile/guile.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/gdb/guile/guile.c b/gdb/guile/guile.c
> index 14b191ded62..e5565b627d9 100644
> --- a/gdb/guile/guile.c
> +++ b/gdb/guile/guile.c
> @@ -677,7 +677,17 @@ gdbscm_initialize (const struct extension_language_defn *extlang)
> "double free or corruption (out)" error.
> Work around the libguile bug by disabling the installation of the
> libgmp memory functions by guile initialization. */
> +
> + /* The scm_install_gmp_memory_functions variable should be removed after
> + version 3.0, so limit usage to 3.0 and before. */
> +#if SCM_MAJOR_VERSION < 3 || (SCM_MAJOR_VERSION == 3 && SCM_MINOR_VERSION == 0)
> + /* This variable is deprecated in Guile 3.0.8 and later but remains
> + available in the whole 3.0 series. */
> +#pragma GCC diagnostic push
> +#pragma GCC diagnostic ignored "-Wdeprecated-declarations"
> scm_install_gmp_memory_functions = 0;
> +#pragma GCC diagnostic pop
> +#endif
>
> /* scm_with_guile is the most portable way to initialize Guile. Plus
> we need to initialize the Guile support while in Guile mode (e.g.,
prev parent reply other threads:[~2022-07-08 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 7:58 [PATCH][gdb/build] " Tom de Vries
2022-07-07 8:14 ` Enze Li
2022-07-07 8:20 ` Tom de Vries
2022-07-07 8:30 ` Enze Li
2022-07-08 14:03 ` Tom de Vries [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=ead1dbfe-3489-4739-735b-ea2325c7323a@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=ludo@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.
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).