From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-libs/libsoup/, net-libs/libsoup/files/
Date: Tue, 16 Jan 2024 03:19:23 +0000 (UTC) [thread overview]
Message-ID: <1705374879.6a20a163ee9cabbe8fc4c6903abdbf1f5baf230b.sam@gentoo> (raw)
commit: 6a20a163ee9cabbe8fc4c6903abdbf1f5baf230b
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Jan 16 03:02:42 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Jan 16 03:14:39 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6a20a163
net-libs/libsoup: fix build w/ libxml2-2.12
Closes: https://bugs.gentoo.org/917556
Signed-off-by: Sam James <sam <AT> gentoo.org>
net-libs/libsoup/files/libxml2-2.12.patch | 36 +++++++++++++++++++++++++++++++
net-libs/libsoup/libsoup-2.74.3.ebuild | 4 +++-
2 files changed, 39 insertions(+), 1 deletion(-)
diff --git a/net-libs/libsoup/files/libxml2-2.12.patch b/net-libs/libsoup/files/libxml2-2.12.patch
new file mode 100644
index 000000000000..3190eeb6301c
--- /dev/null
+++ b/net-libs/libsoup/files/libxml2-2.12.patch
@@ -0,0 +1,36 @@
+https://bugs.gentoo.org/917556
+https://gitlab.gnome.org/GNOME/libsoup/-/commit/ced3c5d8cad0177b297666343f1561799dfefb0d
+
+From ced3c5d8cad0177b297666343f1561799dfefb0d Mon Sep 17 00:00:00 2001
+From: Khem Raj <raj.khem@gmail.com>
+Date: Wed, 22 Nov 2023 18:49:10 -0800
+Subject: [PATCH] Fix build with libxml2-2.12.0 and clang-17
+
+Fixes build errors about missing function prototypes with clang-17
+
+Fixes
+| ../libsoup-2.74.3/libsoup/soup-xmlrpc-old.c:512:8: error: call to undeclared function 'xmlParseMemory'; ISO C99 and later do not support implicit function declarations
+
+Signed-off-by: Khem Raj <raj.khem@gmail.com>
+--- a/libsoup/soup-xmlrpc-old.c
++++ b/libsoup/soup-xmlrpc-old.c
+@@ -11,6 +11,7 @@
+
+ #include <string.h>
+
++#include <libxml/parser.h>
+ #include <libxml/tree.h>
+
+ #include "soup-xmlrpc-old.h"
+--- a/libsoup/soup-xmlrpc.c
++++ b/libsoup/soup-xmlrpc.c
+@@ -17,6 +17,7 @@
+
+ #include <string.h>
+ #include <errno.h>
++#include <libxml/parser.h>
+ #include <libxml/tree.h>
+ #include "soup-xmlrpc.h"
+ #include "soup.h"
+--
+GitLab
diff --git a/net-libs/libsoup/libsoup-2.74.3.ebuild b/net-libs/libsoup/libsoup-2.74.3.ebuild
index 7e1740520995..4287161e6fb3 100644
--- a/net-libs/libsoup/libsoup-2.74.3.ebuild
+++ b/net-libs/libsoup/libsoup-2.74.3.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2022 Gentoo Authors
+# Copyright 1999-2024 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=7
@@ -53,6 +53,8 @@ BDEPEND="
PATCHES=(
# Disable apache tests until they are usable on Gentoo, bug #326957
"${FILESDIR}"/disable-apache-tests.patch
+ # libxml2-2.12 fix, bug #917556
+ "${FILESDIR}"/libxml2-2.12.patch
)
src_prepare() {
next reply other threads:[~2024-01-16 3:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 3:19 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-19 0:25 [gentoo-commits] repo/gentoo:master commit in: net-libs/libsoup/, net-libs/libsoup/files/ Sam James
2021-12-09 17:11 Mart Raudsepp
2021-11-11 18:46 Mart Raudsepp
2020-07-29 11:23 Mart Raudsepp
2020-02-12 11:46 Mart Raudsepp
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=1705374879.6a20a163ee9cabbe8fc4c6903abdbf1f5baf230b.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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