From: "ross at burtonini dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/29926] debuginfod using deprecated curl (since 7.55.0) API, fails to build with 7.87.0
Date: Fri, 06 Jan 2023 15:53:19 +0000 [thread overview]
Message-ID: <bug-29926-10460-0qvs2zXsgh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29926-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29926
Ross Burton <ross at burtonini dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ross at burtonini dot com
--- Comment #3 from Ross Burton <ross at burtonini dot com> ---
I can't reopen this but I'm still seeing errors:
elfutils-0.188/debuginfod/debuginfod-client.c:1330:7: error:
‘CURLOPT_PROTOCOLS’ is deprecated: since 7.85.0. Use CURLOPT_PROTOCOLS_STR
[-Werror=deprecated-declarations]
1330 | curl_easy_setopt_ck(data[i].handle, CURLOPT_PROTOCOLS,
| ^~~~~~~~~~~~~~~~~~~
CURLOPT_PROTOCOLS was deprecated in 7.85.0 and the replacement
CURLOPT_PROTOCOLS_STR introduced in 7.85.0.
May I suggest building without fatal deprecation warnings by default?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-01-06 15:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 15:41 [Bug debuginfod/29926] New: debuginfod using deprecated curl (since 7.55.0) curl " andrew at ishiboo dot com
2022-12-21 16:27 ` [Bug debuginfod/29926] " andrew at ishiboo dot com
2022-12-21 16:31 ` [Bug debuginfod/29926] debuginfod using deprecated curl (since 7.55.0) " andrew at ishiboo dot com
2022-12-21 16:39 ` fche at redhat dot com
2023-01-06 15:53 ` ross at burtonini dot com [this message]
2023-01-10 22:23 ` mark at klomp dot org
2023-01-11 14:17 ` mark at klomp dot 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-29926-10460-0qvs2zXsgh@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@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).